Hi First off, I should say that I would not claim to be a ZFS expert. I think you should post on the zfs-discuss mailing list, as you are more likely to get the attention of a zfs 'expert' across there. (Include a link back to this thread.)
Having said that, for what it's worth, here is what I make of the output you quoted. (Yes, this is the first time I've seen 'zpool status' in the German language, so that does make it difficult for me to understand the status message!) >From 'zpool status' I can see you have a pool called 'usbDisk' on device 'c5t0d0s0'. The output from 'zdb -l' is interesting. All four labels should be identical. But in this case the labels at the start of the disk (0,1) do not match with the labels (2,3) at the end of the disk. The 'zdb' output shows the pool name and path in labels (2,3) match with the 'zpool status', and shows a size of 500,100,497,408 bytes. Labels (0,1) are from a different pool called 'WD', with a different size of 500,103,118,848 bytes. So I speculate that what has happened is that the labels (2,3) are generated from the system to which you currently have the drive connected (OpenSolaris). But labels (0,1) are from another (original - Solaris 10?) system. The Guid's between (0,1) and (2,3) are all completely different. So I think on the current system, the usb drive is appearing to be smaller in size than on the original system. So when you moved the drive from the original system to the current system, initially it would loose sight of labels (2,3) as they would be past the end of the drive and be unreadable, so it would immediately go into an error state. And then somehow in your subsequent attempts to recover the data you have written new labels (2,3) on the disk...:-( ZFS does not currently handle changing disk sizes very well. There is an open Bug on this: http://bugs.opensolaris.org/view_bug.do?bug_id=6753869 6753869 labeling/shrinking a disk in raid-z vdev makes pool un-importable Ok, so I would guess that ZFS is confused because it does not know which pair of labels is the correct one to use. Other output you could quote, that would might be of use, is 'zpool history' and 'prtvtoc <device>'. I would have thought you stand more chance of recovering the data if you can try an import on the original (Ultra25)system, where hopefully it should see the disk with the same size as it was originally. Good luck Nigel Smith -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
