On Wed, 27 Jan 2010, TheJay wrote:
Guys,Need your help. My DEV131 OSOL build with my 21TB disk system somehow got really screwed: This is what my zpool status looks like: NAME STATE READ WRITE CKSUM rzpool2 DEGRADED 0 0 0 raidz2-0 DEGRADED 0 0 0 replacing-0 DEGRADED 0 0 0 c6t1d0 OFFLINE 0 0 0 c6t16d0 ONLINE 0 0 0 256M resilvered c6t2d0s2 ONLINE 0 0 0 c6t3d0p0 ONLINE 0 0 0 c6t4d0p0 ONLINE 0 0 0 c6t5d0p0 ONLINE 0 0 0 c6t6d0p0 ONLINE 0 0 0 c6t7d0p0 ONLINE 0 0 0 c6t8d0p0 ONLINE 0 0 0 c6t9d0 ONLINE 0 0 0 raidz2-1 DEGRADED 0 0 0 c6t0d0 ONLINE 0 0 0 c6t1d0 UNAVAIL 0 0 0 cannot open c6t10d0 ONLINE 0 0 0 c6t11d0 ONLINE 0 0 0 c6t12d0 ONLINE 0 0 0 c6t13d0 ONLINE 0 0 0 c6t14d0 ONLINE 0 0 0 c6t15d0 ONLINE 0 0 0 check drive c6t1d0 -> It appears in both raidz2-0 and raidz2-1 !!How do I *remove* the drive from raidz2-1 (with edit/hexedit or anything else) it is clearly a bug in ZFS that allowed me to assign the drive twice....again: running DEV131 OSOL
Could you send us the zpool history output? It'd be interesting to know how this happened. Anyway, the way to get out of this is to do a 'zpool detach' on c6d1s0 after the resilvering finishes, and then do a 'zpool online' of c6d1s0 to connect it back up to raidz2-1.
Regards, markm _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
