Hi Jim, That looks interesting though, I'm not a zfs expert by any means but look at some of the properties of the children elements of the mirror:-
version=3 name='zmir' state=0 txg=770 pool_guid=5904723747772934703 vdev_tree type='root' id=0 guid=5904723747772934703 children[0] type='mirror' id=0 guid=15067187713781123481 metaslab_array=15 metaslab_shift=28 ashift=9 asize=36690722816 children[0] type='disk' id=0 guid=8544021753105415508 [b]path='/dev/dsk/c3t3d0s0'[/b] devid='id1,[EMAIL PROTECTED]/a' whole_disk=1 [b]is_spare=1[/b] DTL=19 children[1] type='disk' id=1 guid=3579059219373561470 [b]path='/dev/dsk/c3t4d0s0'[/b] devid='id1,[EMAIL PROTECTED]/a' whole_disk=1 [b]is_spare=1[/b] DTL=20 If those are the original path ids, and you didn't move the disks on the bus? Why is the is_spare flag set? There are a lot of options to zdb, some can produce a lot of output. Try zdb zmir Check the drive label contents with zdb -l /dev/dsk/c3t0d0s0 zdb -l /dev/dsk/c3t1d0s0 zdb -l /dev/dsk/c3t3d0s0 zdb -l /dev/dsk/c3t4d0s0 Uberblock info with zdb -uuu zmir And dataset info with zdb -dd zmir There are more options, and they give even more info if you repeat the option letter more times ( especially the -d flag... ) These might be worth posting to help one of the developers spot something. Cheers, Alan This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
