[FUG-BR] FreeBsd 8.2 e geom_stripe

Paulo Henrique - BSDs Brasil paulo.rddck em bsd.com.br
Sábado Agosto 13 23:00:07 BRT 2011


Por que estamos recebendo essa mensagem ?
Começou ontem !!

Em 13/08/2011 22:50, service-clients em sc.sfr.fr escreveu:
> Vous souhaitez prendre contact avec le Service Client. Votre demande n'a pas été délivrée. Pour contacter le service client par mail, merci d'utiliser le formulaire prévu à cet effet dans la rubrique "Nous contacter" sur le site www.sfr.fr. Ce message a été envoyé par un automate : merci de ne pas y répondre. .
>
> ----- Original Message -----
> From: Eder Souza<eder.souza em bsd.com.br>
> Sent: samedi 13 août 2011 22 h 46 GMT-03:00
> Subject: [FUG-BR] FreeBsd 8.2 e geom_stripe
>
>    
>> Olá pessoal !!
>> Estou usando "GPT" no FreeBSD para criar partições grandes e em conjunto
>> com o gstripe criei vários slices em dois hds distintos para juntar todas
>> ganhando um maior armazenamento!
>>
>> Para meu HD ad5
>>
>> gpart list ad5
>> Geom name: ad5
>> state: OK
>> fwheads: 16
>> fwsectors: 63
>> last: 5860533134
>> first: 34
>> entries: 128
>> scheme: GPT
>> Providers:
>> 1. Name: ad5s1
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 091bc6ae-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 32256
>>    type: freebsd
>>    index: 1
>>    end: 601882686
>>    start: 63
>> 2. Name: ad5s2
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 1145bc16-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 308163935744
>>    type: freebsd
>>    index: 2
>>    end: 1203765310
>>    start: 601882687
>> 3. Name: ad5s3
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 11d36db4-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 616327839232
>>    type: freebsd
>>    index: 3
>>    end: 1805647934
>>    start: 1203765311
>> 4. Name: ad5s4
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 1234d863-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 924491742720
>>    type: freebsd
>>    index: 4
>>    end: 2407530558
>>    start: 1805647935
>> 5. Name: ad5s5
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 12a0d7d2-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 1232655646208
>>    type: freebsd
>>    index: 5
>>    end: 3009413182
>>    start: 2407530559
>> 6. Name: ad5s6
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 130391ab-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 1540819549696
>>    type: freebsd
>>    index: 6
>>    end: 3611295806
>>    start: 3009413183
>> 7. Name: ad5s7
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 1369a442-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 1848983453184
>>    type: freebsd
>>    index: 7
>>    end: 4213178430
>>    start: 3611295807
>> 8. Name: ad5s8
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 13cea7cc-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 2157147356672
>>    type: freebsd
>>    index: 8
>>    end: 4815061054
>>    start: 4213178431
>> 9. Name: ad5s9
>>    Mediasize: 308163903488 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawuuid: 144a1bce-c4de-11e0-b143-00270e19aa68
>>    rawtype: 516e7cb4-6ecf-11d6-8ff8-00022d09712b
>>    label: (null)
>>    length: 308163903488
>>    offset: 2465311260160
>>    type: freebsd
>>    index: 9
>>    end: 5416943678
>>    start: 4815061055
>> Consumers:
>> 1. Name: ad5
>>    Mediasize: 3000592982016 (2.7T)
>>    Sectorsize: 512
>>    Mode: r9w9e27
>>
>> *************************************************************
>> E para o meu HD ad6 onde está o SO BSD ainda usando o scheme MBR portando
>> particionar até 4 ...
>>
>> gpart list ad6
>> Geom name: ad6
>> state: OK
>> fwheads: 16
>> fwsectors: 63
>> last: 1953525167
>> first: 63
>> entries: 4
>> scheme: MBR
>> Providers:
>> 1. Name: ad6s1
>>    Mediasize: 75161608704 (70G)
>>    Sectorsize: 512
>>    Mode: r6w6e11
>>    attrib: active
>>    rawtype: 165
>>    length: 75161608704
>>    offset: 32256
>>    type: freebsd
>>    index: 1
>>    end: 146800079
>>    start: 63
>> 2. Name: ad6s2
>>    Mediasize: 308163889152 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawtype: 165
>>    length: 308163889152
>>    offset: 75161640960
>>    type: freebsd
>>    index: 2
>>    end: 748682675
>>    start: 146800080
>> 3. Name: ad6s3
>>    Mediasize: 308163889152 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawtype: 165
>>    length: 308163889152
>>    offset: 383325530112
>>    type: freebsd
>>    index: 3
>>    end: 1350565271
>>    start: 748682676
>> 4. Name: ad6s4
>>    Mediasize: 308163889152 (287G)
>>    Sectorsize: 512
>>    Mode: r1w1e2
>>    rawtype: 165
>>    length: 308163889152
>>    offset: 691489419264
>>    type: freebsd
>>    index: 4
>>    end: 1952447867
>>    start: 1350565272
>> Consumers:
>> 1. Name: ad6
>>    Mediasize: 1000204886016 (932G)
>>    Sectorsize: 512
>>    Mode: r9w9e26
>>
>> Agrupei todas com o mesmo tamanho ...
>> gstripe label -v st0 /dev/ad5s1 /dev/ad5s2 /dev/ad5s3 /dev/ad5s4 /dev/ad5s5
>> /dev/ad5s6 /dev/ad5s7 /dev/ad5s8 /dev/ad5s9 /dev/ad6s2 /dev/ad6s3 /dev/ad6s4
>>
>> estou subindo com o meu sysctl :
>> kern.geom.debugflags=16
>> kern.geom.label.gptid.enable=0
>>
>> O módulo geom_stripe está subindo no loader.cf
>>
>> Apos formatar montei minha partição sem problemas:
>> mount /dev/stripe/st0 /backup
>>
>> até ae tudo funcionando df -lah
>>
>> /dev/stripe/st0    3.3T    4.0K    3.0T     0%    /backup
>>
>> Tenho 3.3 Teras montados e funcional...
>>
>> O problema são os logs após o boot:
>> /var/log/messages
>>
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s2 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s3 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s4 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s5 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s6 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s7 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s8 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s9 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s1 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM: ufsid/4e43f45beaac8665s1: geometry does
>> not match label (255h,63s != 16h,63s).
>> Aug 12 09:31:47 img kernel: GEOM: ufsid/4e43f45beaac8665s1: media size does
>> not match label.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s2 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s3 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s4 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s5 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s6 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s7 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s8 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e43f45beaac8665s9 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451ba505e404ed to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM: ufsid/4e451ba505e404ed: geometry does not
>> match label (255h,63s != 16h,63s).
>> Aug 12 09:31:47 img kernel: GEOM: ufsid/4e451ba505e404ed: media size does
>> not match label.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/091bc6ae-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM:
>> gptid/091bc6ae-c4de-11e0-b143-00270e19aa68: geometry does not match label
>> (255h,63s != 16h,63s).
>> Aug 12 09:31:47 img kernel: GEOM:
>> gptid/091bc6ae-c4de-11e0-b143-00270e19aa68: media size does not match label.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451babe8b023d2 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/1145bc16-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bb1acbba4d0 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/11d36db4-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bb8284b2c59 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/1234d863-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bc03e9e830b to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/12a0d7d2-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bc6e9349940 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/130391ab-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bccb7430652 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/1369a442-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bd3e61d8fe1 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/13cea7cc-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bddb1c72b00 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> gptid/144a1bce-c4de-11e0-b143-00270e19aa68 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s2 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s3 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s4 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Device st0 activated.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451be7b445ae8a to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bf120de74d1 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM: stripe/st0: media size does not match
>> label.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Cannot add disk
>> ufsid/4e451bfdf8434247 to st0 (error=17).
>> Aug 12 09:31:47 img kernel: GEOM: ufsid/4e451c564991ff4a: media size does
>> not match label.
>>
>>
>> ********************************
>>
>> Nos logs podemos notar que os meus discos estão sendo adicionados durante o
>> boot sem problemas nesta parte.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s2 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s3 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s4 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s5 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s6 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s7 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s8 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad5s9 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s2 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s3 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Disk ad6s4 attached to st0.
>> Aug 12 09:31:47 img kernel: GEOM_STRIPE: Device st0 activated.
>>
>> Tudo continua funcionando tranquilamente, mas fiquei pouco confiante de
>> colocar algo em produção com estes erros todos, alguem sabe me informar o q
>> é isso ?
>>
>> Eder
>> -------------------------
>> Histórico: http://www.fug.com.br/historico/html/freebsd/
>> Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd
>>      
> -------------------------
> Histórico: http://www.fug.com.br/historico/html/freebsd/
> Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd
>    


-- 
Paulo Henrique.
Consultória em Projetos de TI.

Pessoas normais, conversam sobre pessoas
Pessoas inteligentes, conversam sobre fatos
Pessoas Excepcionais, conversam sobre conceitos
Porem prefiro ficar mudo
Afinal, não sou normal
Não me creo que seja inteligente
E ainda cometo erros para ser considerado excepicional

Desenvolvedor de Software
Administrador de Sitemas.
Genuine BSD/Unix User.


Mais detalhes sobre a lista de discussão freebsd