Kyle Kakligian gmail.com> writes:
> 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
SOLVED
According to `zdb -l /dev/rdsk/`, 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,
On Thu, Mar 5, 2009 at 1:09 PM, Kyle Kakligian wrote:
> On Wed, Mar 4, 2009 at 7:59 PM, Richard Elling
> wrote:
>> additional comment below...
>>
>> Kyle Kakligian wrote:
>>>
>>> On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
>>>
that link suggests that this is a problem with a dirty ex
On Wed, Mar 4, 2009 at 7:59 PM, Richard Elling wrote:
> additional comment below...
>
> Kyle Kakligian wrote:
>>
>> On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
>>
>>>
>>> that link suggests that this is a problem with a dirty export:
>>>
>>
>> Yes, a loss of power should mean there was no clean
additional comment below...
Kyle Kakligian wrote:
On Mon, Mar 2, 2009 at 8:30 AM, Blake 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.
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
maybe try import
On Mon, Mar 2, 2009 at 8:30 AM, Blake 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.
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> maybe try importing on system A again, doing a 'zpool export', waiting
> for co
On Mon, Mar 2, 2009 at 8:30 AM, Blake 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.
On Mon, Mar 2, 2009 at 8:30 AM, Blake wrote:
> maybe try importing on system A again, doing a 'zpool export', waiting
> for co
that link suggests that this is a problem with a dirty export:
http://www.sun.com/msg/ZFS-8000-EY
maybe try importing on system A again, doing a 'zpool export', waiting
for completion, then moving to system B to import?
On Sun, Mar 1, 2009 at 2:29 PM, Kyle Kakligian wrote:
> What does it mean f
What does it mean for a vdev to have an invalid configuration and how
can it be fixed or reset? As you can see, the following pool can no
longer be imported: (Note that the "last accessed by another system"
warning is because I moved these drives to my test workstation.)
~$ zpool import -f pool0
c
