On Thu, May 29, 2008 at 8:59 PM, Joe Little <[EMAIL PROTECTED]> wrote:
> On Thu, May 29, 2008 at 7:25 PM, Jeb Campbell <[EMAIL PROTECTED]> wrote:
>> Meant to add that zpool import -f pool doesn't work b/c of the missing log
>> vdev.
>>
>> All the other disks are there and show up with "zpool import", but it won't
>> import.
>>
>> Is there anyway a util could clear the log device vdev from the remaining
>> raidz2 devices?
>>
>> Then I could import just a standard raidz2 pool.
>>
>> I really love zfs (and had recently upgraded to 6 disks in raidz2), but this
>> is *really* gonna hurt to lose all this stuff (yeah, the work stuff is
>> backed up, but I have/had tons of personal stuff on there).
>>
>> I definitely would prefer to just sit tight, and see if there is any way to
>> get this going (read only would be fine).
>>
More to the point, does it say there are any permanent errors that you
find? Again, I was able to import it after reassigning the log device
so it thinks its there. I got to this point:
[EMAIL PROTECTED]:~# zpool status -v
pool: data
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 24
raidz1 ONLINE 0 0 24
c2t0d0 ONLINE 0 0 0
c2t1d0 ONLINE 0 0 0
c1t1d0 ONLINE 0 0 0
logs ONLINE 0 0 24
c3t1d0 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
data/home:<0x0>
Yes, because of the "error" I can no longer have any mounts created at
import, but the "zfs mount data/proj" or other filesystem, but not
data/home, is still possible. Again, I think that you will want to use
"-o ro" as an option to that mount command to not have the system go
bonkers. Check my blog for more info on reseting the log device for a
"zfs replace" action -- which itself puts you into more troubling
position of possibly having corruptions from the resilver, but at
least for me allowed me to mount the pool for read-only mounts of the
remaining filesystems.
>
> You can mount all those filesystems, and then zfs send/recv them off
> to another box. Its sucks, but as of now, there is no re-importing of
> the pool UNTIL the log can be removed. Sadly, I think that log removal
> will at least require importation of the pool in question first. For
> some reason you already can't import your pool.
>
> In my case, I was running B70 and could import the pool still, but
> just degraded. I think that once you are at a higher rev (which I do
> not know, but inclusive of B82 and B85), you won't be able to import
> it anymore when it fails.
>
>
>> Jeb
>>
>>
>> This message posted from opensolaris.org
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss@opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>>
>
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
