SOLVED According to `zdb -l /dev/rdsk/<vdev>`, one of my drives was missing two of its four redundant labels. (#2 and #3) These two are next to each other at the end of the device so it makes some sense that they could both be garbled.
I'm not sure why `zfs import` choked on this [typical?] error case, but its easy to fix with a very careful dd. I took a different and very roundabout approach to recover my data, however, since I'm not confident in my 'careful' skills. (after all, where's my backup?) Instead, on a linux workstation where I am more cozy, I compiled zfs-fuse from the source with a slight modification to ignore labels 2 and 3. fusermount worked great and I recovered my data without issue. Thanks to everyone for all the help. I'm impressed by the amount of community support here on the list! On Fri, Mar 6, 2009 at 12:17 AM, Joe S <js.li...@gmail.com> wrote: > On Thu, Mar 5, 2009 at 1:09 PM, Kyle Kakligian <kaklig...@google.com> wrote: >> On Wed, Mar 4, 2009 at 7:59 PM, Richard Elling <richard.ell...@gmail.com> >> wrote: >>> additional comment below... >>> >>> Kyle Kakligian wrote: >>>> >>>> On Mon, Mar 2, 2009 at 8:30 AM, Blake <blake.ir...@gmail.com> wrote: >>>> >>>>> >>>>> that link suggests that this is a problem with a dirty export: >>>>> >>>> >>>> Yes, a loss of power should mean there was no clean export. >>>> > > Hmmm. I was under the impression that a power loss wouldn't pose a > threat to my ZFS filesystems.. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
