On 2013-Jan-08 21:30:57 -0800, John Giannandrea <j...@meer.net> wrote:
>Notice that in the absence of the faulted da2 the OS has assigned da3 to da2 
>etc.  I suspect this was part of the original problem in creating a label with 
>two da2s

The primary vdev identifier is tha guid.  Tha path is of secondary
importance (ZFS should automatically recover from juggled disks
without an issue - and has for me).

Try running "zdb -l" on each of your pool disks and verify that
each has 4 identical labels, and that the 5 guids (one on each
disk) are unique and match the vdev_tree you got from zdb.

My suspicion is that you've somehow "lost" the disk with the guid

>twa0: <3ware 9000 series Storage Controller>
>twa0: INFO: (0x15: 0x1300): Controller details:: Model 9500S-8, 8 ports, 
>Firmware FE9X
>da0 at twa0 bus 0 scbus0 target 0 lun 0
>da1 at twa0 bus 0 scbus0 target 1 lun 0
>da2 at twa0 bus 0 scbus0 target 2 lun 0
>da3 at twa0 bus 0 scbus0 target 3 lun 0
>da4 at twa0 bus 0 scbus0 target 4 lun 0

Are these all JBOD devices?

Peter Jeremy

Attachment: pgpykCYjUFT7j.pgp
Description: PGP signature

zfs-discuss mailing list

Reply via email to