xfs-masters
[Top] [All Lists]

[Bug 817] XFS driver oops when trying to mount "dirty" filesystem.

To: xfs-masters@xxxxxxxxxxx
Subject: [Bug 817] XFS driver oops when trying to mount "dirty" filesystem.
From: bugzilla-daemon@xxxxxxxxxxx
Date: Mon, 23 Mar 2009 07:56:40 -0500
Auto-submitted: auto-generated
In-reply-to: <bug-817-113@xxxxxxxxxxxxxxxx/bugzilla/>
References: <bug-817-113@xxxxxxxxxxxxxxxx/bugzilla/>
http://oss.sgi.com/bugzilla/show_bug.cgi?id=817





--- Comment #8 from Vadim V. Galitsyn <galitsyn@xxxxxxxxx>  2009-03-23 07:56:37 
CST ---
(In reply to comment #7)
> (In reply to comment #6)
> ...
> > > do you have barriers enabled?
> > 
> > How can I check that?
> 
> check dmesg after a mount; if barrier writes failed you'll get a notice
According to the facts that

- "write barrier support is enabled by default in XFS since kernel version
2.6.17";
- I have no specific mount options during mount;

So, I guess, barriers are enabled, however I do not see any barrier related
logs after mount.

> 
> > > Is DM or MD involved somehow?
> > No
> > 
> > I have observed that the issue can be reduced in case I will do xfs_repair 
> > just
> > before mount. After that the problem was not reproduced anymore (for 
> > partition
> > to which I have applied xfs_repair).
> 
> how did you invoke xfs_repair?  If it was with -L then that's quite expected,
> you erased the log, so there was no log replay to oops in.

Yes, it was with -L option.

-- 
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

<Prev in Thread] Current Thread [Next in Thread>