Further to this, I've considered doing the following: 1) Doing a zpool destroy on the volume 2) Doing a zpool import -D on the volume
It would appear to me that primarily what has occurred is one or all of the metadata stores ZFS has created have become corrupt? Will a zpool import -D ignore metadata and rebuild using some magic foo? I still don't understand how even if an entire array became broken these issues were then synced to the backup array. Confused and bewildered, Stuart :) On Wed, 2007-02-28 at 16:55 -0800, Eric Schrock wrote: > On Thu, Mar 01, 2007 at 10:50:28AM +1000, Stuart Low wrote: > > Heya, > > > > > Sorry. Try 'echo vdev_load::dis | mdb -k'. This will give the > > > disassembly for vdev_load() in your current kernel (which will help us > > > pinpoint what vdev_load+0x69 is really doing). > > > > Ahh, thanks for that. > > <snip> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
