Kernel BUG when running xfs_fsr with 2.6.35.1

[Arto Jantunen]

Dave Chinner <david at fromorbit.com> writes:
>> I had a kernel BUG yesterday when running xfs_fsr on my Debian Unstable
>> laptop. The kernel is upstream 2.6.35.1. I'm attaching the backtrace
>> below. I haven't tried reproducing the problem yet and don't know if it is
>> reproducible. I can try that, and test patches etc. if it is useful. Let me
>> know if there is any other information I can provide to help with debugging.
>
> It's not obvious what has gone wrong at all - I haven't seen
> anything like this in all my recent testing, so it's something new.
> The first oops implies the inode has not been joined to the
> transaction, but from code inspection I cannot see how that can
> happen.

I tried to reproduce the problem, and this time xfs_fsr finished without
reporting errors, but the kernel output the following two lines (one of which
is essentially empty):

[ 6372.878945] Filesystem "sda4": Access to block zero in inode 67203861
start_block: 0 start_off: 0 blkcnt: 0 extent-state: 0 lastx: 2
[ 6372.878950]

I decided to boot from a usb stick and try xfs_repair -n, I have attached the
output of that. There were errors reported. Is this simply a case of random
(possibly hardware related) fs corruption, or were the errors actually caused
by the xfs_fsr run that crashed the system? Is there a way to tell from this
data, is there anything else I can provide?

-- 
Arto Jantunen

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xfsrep
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20100817/9ef03608/attachment.bat>