?
This was referring to the second BUG_ON in the logs. I checked the first
BUG_ON again and see:
kernel: [ 100.963478] kernel BUG at
/build/buildd/linux-3.2.0/fs/btrfs/extent-tree.c:4816!
RAX: ea01
4815 if (iref) {
4816 BUG_ON(!found_extent);
4817
On Tue, Nov 29, 2011 at 02:39:26AM +0100, Karl Mardoff Kittilsen wrote:
Hi!
Sending a mail on this issue, as advised on IRC.
My /home file system fails to mount and the kernel seem to freeze
and I need to do the Alt+SysRq RSNEIUB routine to boot it safely.
The corruption happened on a
Den 29. nov. 2011 16:12, skrev Chris Mason:
On Tue, Nov 29, 2011 at 02:39:26AM +0100, Karl Mardoff Kittilsen wrote:
Hi!
Sending a mail on this issue, as advised on IRC.
My /home file system fails to mount and the kernel seem to freeze
and I need to do the Alt+SysRq RSNEIUB routine to boot it
On Tue, Nov 29, 2011 at 04:29:54PM +0100, Karl Mardoff Kittilsen wrote:
Den 29. nov. 2011 16:12, skrev Chris Mason:
On Tue, Nov 29, 2011 at 02:39:26AM +0100, Karl Mardoff Kittilsen wrote:
Hi!
Sending a mail on this issue, as advised on IRC.
My /home file system fails to mount and the
On Tue, Nov 29, 2011 at 10:49:13AM -0500, Chris Mason wrote:
The good news about this one is that it is very clear cut. The hard
part is figuring out where these bogus link counts came from.
I'd suggest that you spend some time running memtest on the machine.
Just to add some evidence from
On Tue, Nov 29, 2011 at 05:47:46PM +0100, David Sterba wrote:
On Tue, Nov 29, 2011 at 10:49:13AM -0500, Chris Mason wrote:
The good news about this one is that it is very clear cut. The hard
part is figuring out where these bogus link counts came from.
I'd suggest that you spend some
:30 karl-precise kernel: [ 100.963478] kernel BUG at
/build/buildd/linux-3.2.0/fs/btrfs/extent-tree.c:4816!
Nov 29 01:17:30 karl-precise kernel: [ 100.963516] invalid opcode:
[#1] SMP
Nov 29 01:17:30 karl-precise kernel: [ 100.963534] CPU 3
Nov 29 01:17:30 karl-precise kernel
