- 1. Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Arto Jantunen <viiru@xxxxxxxxxx>
- Date: Mon, 16 Aug 2010 11:32:29 +0300
- Hi List, 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 ye
- /archives/xfs/2010-08/msg00161.html (15,314 bytes)
- 2. Re: Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Tue, 17 Aug 2010 08:09:41 +1000
- 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 transactio
- /archives/xfs/2010-08/msg00166.html (7,951 bytes)
- 3. Re: Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Arto Jantunen <viiru@xxxxxxxxxx>
- Date: Tue, 17 Aug 2010 12:19:29 +0300
- I used the compiler which is available on current Debian Testing, --version reports "gcc (Debian 4.4.4-8) 4.4.5 20100728 (prerelease)". I'll try to reproduce the problem later today. -- Arto Jantunen
- /archives/xfs/2010-08/msg00178.html (8,536 bytes)
- 4. Re: Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Arto Jantunen <viiru@xxxxxxxxxx>
- Date: Tue, 17 Aug 2010 20:05:35 +0300
- 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
- /archives/xfs/2010-08/msg00182.html (19,166 bytes)
- 5. Re: Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Wed, 18 Aug 2010 09:03:57 +1000
- That's a corrupt extent record - it's all zeros, and judging by the fact that it's only got 2 extents, it's probaly inline in the inode (i.e. the inode fork has been zeroed.) .... Ok, so a corrupt se
- /archives/xfs/2010-08/msg00185.html (11,952 bytes)
- 6. Re: Kernel BUG when running xfs_fsr with 2.6.35.1 (score: 1)
- Author: Arto Jantunen <viiru@xxxxxxxxxx>
- Date: Wed, 18 Aug 2010 11:48:22 +0300
- Could this corruption have been caused by having to reboot via sysrq after the original crash (with sync, umount, sync, reboot)? Other than that one, I don't remember having any power failures or suc
- /archives/xfs/2010-08/msg00188.html (14,074 bytes)
This search system is powered by
Namazu