Hi Lukas, I've encountered a problem similar to yours where a zfs pool became unaccessible after a reboot with the error "The pool metadata is corrupted." In my case I'm running on Solaris 10 8/07 127112-11. Can you explain how you determined the offsets for modifying vdev_uberblock_compare, and if it is possible to do so without source code since this is on Solaris 10? I'd also be willing to put the drive on a nevada box but the current download is build 85 so I suspect there will be some difference with your build 78 examples anyways.
You're the only person I've seen who has been able to recover from this error so I would greatly appreciate more detail on how you got access to your data again. Thanks! James Lick > I managed to recover my data after 3 days fighting. > ... > > > vdev_uberblock_compare+0x49/W 1 > vdev_uberblock_compare+0x49: 0xffffffff = > 0x1 > _uberblock_compare+0x3b/W 1 > vdev_uberblock_compare+0x3b: 0xffffffff = > 0x1 > fs_setup+0x60/v 0xeb > zfsvfs_setup+0x60: 0x74 = 0xeb > > These changes allowed me to import zpool and now I'm > coping data. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
