Moshe,

You might want to check if you have multiple paths to these disks.

- Sanjeev
On Wed, Feb 17, 2010 at 07:59:28PM -0800, Moshe Vainer wrote:
> I have another very weird one, looks like a reoccurance of the same issue but 
> with the new firmware.
> 
> We have the following disks:
> 
> AVAILABLE DISK SELECTIONS:
>        0. c7t1d0 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,0
>        1. c7t1d1 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,1
>        2. c7t1d2 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,2
>        3. c7t1d3 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,3
>        4. c7t1d4 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,4
>        5. c7t1d5 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,5
>        6. c7t1d6 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,6
>        7. c7t1d7 <DEFAULT cyl 60797 alt 2 hd 255 sec 126>
>           /p...@0,0/pci8086,3...@3/pci17d3,1...@0/d...@1,7
> 
> rpool uses c7d1d7
> 
> # zpool status
>   pool: rpool
>  state: ONLINE
>  scrub: none requested
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         rpool       ONLINE       0     0     0
>           c7t1d7s0  ONLINE       0     0     0
> 
> errors: No known data errors
> 
> 
> I tried to create the following tank:
> 
> zpool create -f tank \
>         raidz2 \
>                 c7t1d0 \
>                 c7t1d1 \
>                 c7t1d2 \
>                 c7t1d3 \
>                 c7t1d4 \
>                 c7t1d5 \
>         spare \
>                 c7t1d6
> 
> # ./mktank.sh
> invalid vdev specification
> the following errors must be manually repaired:
> /dev/dsk/c7t1d7s0 is part of active ZFS pool rpool. Please see zpool(1M).
> 
> So clearly, it confuses one of the other drives with c7t1d7
> 
> What's even weirder - this is after a clean reinstall of solaris (it's a test 
> box). 
> Any ideas on how to clean the state?
> James, if you read this, is this the same issue?
> 
> Thanks in advance, 
> Moshe
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

-- 
----------------
Sanjeev Bagewadi
Solaris RPE 
Bangalore, India
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to