Arne,
On 06/13/2010 03:57 PM, Arne Jansen wrote:
> Thomas Nau wrote:
>> Dear all
>>
>> We ran into a nasty problem the other day. One of our mirrored zpool
>> hosts several ZFS filesystems. After a reboot (all FS mounted at that
>> time an in use) the machine paniced (console output further down). After
>> detaching one of the mirrors the pool fortunately imported automatically
>> in a faulted state without mounting the filesystems. Offling the
>> unplugged device and clearing the fault allowed us to disable
>> auto-mounting the filesystems. Going through them one by one all but one
>> mounted OK. The one again triggered a panic. We left mounting on that
>> one disabled for now to be back in production after pulling data from
>> the backup tapes. Scrubbing didn't show any error so any idea what's
>> behind the problem? Any chance to fix the FS?
>
> We had the same problem. Victor pointed my to
>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6742788
>
> with a workaround to mount the filesystem read-only to save the data.
> I still hope to figure out the chain of events that causes this. Did you
> use any extended attributes on this filesystem?
>
> --
> Arne
Mounting the FS read-only worked, thanks again. I checked the attributes
and the set for all files is:
{archive,nohidden,noreadonly,nosystem,noappendonly,nonodump,noimmutable,av_modified,noav_quarantined,nonounlink}
so just the default ones
Thomas
-----------------------------------------------------------------
GPG fingerprint: B1 EE D2 39 2C 82 26 DA A5 4D E0 50 35 75 9E ED
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
