http://bugzilla.kernel.org/show_bug.cgi?id=6957
------- Additional Comments From nathans@xxxxxxx 2006-08-10 15:43 -------
Your oops is due to some rather braindead code in XFS that tries to
catch inode corruption in the form of an extent which points at the
primary superblock as its start (which is a really bad place to then
go write). This code shouldn't be causing a panic, it should rather
be reporting the corrupt file and battling on. I'll fix that.
But, that aside, the root issue here seems to be related to logging
and/or recovery of the log. Usual initial question here is are you
running with any form of I/O completion ordering guarantees? Looks
like SATA and device mapper from your report, so I'm guessing not..
could you try your test with a single drive (no DM/LVM), and with
the barrier mount option (this is the default in recent kernels),
just to see if that fares any better. If it does, it will point our
investigation in one direction, if not we'll need to look elsewhere.
One other question - are you saying you always see this same panic
when you run the test (several times, till it eventually fails)?
thanks.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|