BTRFS crash during mount

DISCUSSION Daniel Kuhn 3 participants 4 messages Feb 8, 2012 – Feb 13, 2012 Btrfs file system

Share & tools

Daniel Kuhn

author

2012-02-08 22:19 UTC #0 lore raw

After a forced power turn-off the filesystem of my primary boot partition cannot be mounted anymore,
btrfs crashes during the mount process. I'm using OpenSuse 12.1 but I've also tried mounting with a newer kernel 3.2.2 (systemrescue cd) and with a usb-converter connected to another PC without success.

The kernel log seems pretty specific about the crash location, see below.

Best regards,
Daniel Kuhn

[   66.476674] ------------[ cut here ]------------
[   66.476684] kernel BUG at fs/btrfs/free-space-cache.c:1515!
[   66.476691] invalid opcode: 0000 [#1] SMP
[   66.476699] Modules linked in: tpm_tis tpm tpm_bios i2c_nforce2 serio_raw pcspkr floppy k10temp asus_atk0110 raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear ata_generic nouveau ttm drm_kms_helper drm i2c_algo_bit firewire_ohci i2c_core pata_acpi mxm_wmi forcedeth pata_marvell firewire_core pata_amd video wmi
[   66.476752]
[   66.476759] Pid: 1844, comm: mount Not tainted 3.2.2-alt250-i586 #2 System manufacturer System Product Name/M3N-HT DELUXE
[   66.476772] EIP: 0060:[<c06f7b6f>] EFLAGS: 00010206 CPU: 2
[   66.476785] EIP is at remove_from_bitmap+0xa8/0x285
[   66.476792] EAX: 6a92c000 EBX: 00000000 ECX: 0005c000 EDX: 00000002
[   66.476799] ESI: f2f5baa8 EDI: f2f5ba8c EBP: f2f5ba48 ESP: f2f5b9ec
[   66.476805]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   66.476813] Process mount (pid: 1844, ti=f2f5a000 task=f2ff7080 task.ti=f2f5a000)
[   66.476818] Stack:
[   66.476822]  f2f5ba2c 00000385 00000000 f2f5ba58 f2750370 f2f5ba48 f2f5ba44 f2f5ba40
[   66.476837]  00000019 71bfffff 00000002 71c00000 00000002 f3159600 073ba000 00000000
[   66.476851]  0005c000 00000000 6a92c000 00000002 f2f5baa8 00000000 f2750370 f2f5baa0
[   66.476865] Call Trace:
[   66.476877]  [<c06f9bf4>] btrfs_remove_free_space+0x34c/0x370
[   66.476889]  [<c06bcfa3>] btrfs_alloc_logged_file_extent+0x114/0x211
[   66.476900]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476909]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476919]  [<c06f5afd>] replay_one_extent+0x470/0x5f2
[   66.476929]  [<c050ef9a>] ? __fsnotify_inode_delete+0x8/0xa
[   66.476941]  [<c06f6f55>] replay_one_buffer+0x1d6/0x229
[   66.476950]  [<c06f2cfe>] walk_down_log_tree+0x15b/0x2cd
[   66.476959]  [<c06f3062>] walk_log_tree+0x71/0x188
[   66.476968]  [<c06f5011>] btrfs_recover_log_trees+0x24a/0x257
[   66.476977]  [<c06f6d7f>] ? add_inode_ref+0x480/0x480
[   66.476987]  [<c06c78b8>] open_ctree+0x116a/0x1415
[   66.476998]  [<c06ac8a6>] btrfs_mount+0x43b/0x749
[   66.477009]  [<c04bf7b1>] ? cpumask_next+0x12/0x14
[   66.477018]  [<c04c0729>] ? pcpu_alloc+0x6ca/0x6ff
[   66.477027]  [<c0768c3a>] ? ida_get_new_above+0x14a/0x164
[   66.477036]  [<c04f9aa5>] ? alloc_vfsmnt+0x80/0x111
[   66.477046]  [<c04d9236>] ? __kmalloc_track_caller+0x134/0x13e
[   66.477055]  [<c04e86bf>] mount_fs+0x62/0x139
[   66.477064]  [<c04f9ff5>] vfs_kern_mount+0x4f/0x7b
[   66.477073]  [<c04fafef>] do_kern_mount+0x38/0xb6
[   66.477082]  [<c04fb67c>] do_mount+0x60f/0x65c
[   66.477090]  [<c04bcf78>] ? strndup_user+0x29/0x3a
[   66.477098]  [<c04fb731>] sys_mount+0x68/0x94
[   66.477108]  [<c09c69bc>] syscall_call+0x7/0xb
[   66.477112] Code: e4 8d 55 e4 89 45 e8 8b 45 d8 8d 4d ec 89 14 24 8b 55 b4 e8 c6 f8 ff ff 85 c0 78 0f 8b 55 f0 3b 57 04 8b 45 ec 75 04 3b 07 74 04 <0f> 0b eb fe 8b 4d b4 8b 5d b4 8b 49 0c 89 4d dc 8b 4b 10 39 ca
[   66.477179] EIP: [<c06f7b6f>] remove_from_bitmap+0xa8/0x285 SS:ESP 0068:f2f5b9ec
[   66.477235] ---[ end trace 2e72e8358ee32e95 ]---

cwillu

2012-02-08 23:00 UTC #1 lore raw

On Wed, Feb 8, 2012 at 4:19 PM, Daniel Kuhn <[email protected]> wro= te:

Quoted 1 line

After a forced power turn-off the filesystem of my primary boot parti=

tion

Quoted 2 lines

cannot be mounted anymore,
btrfs crashes during the mount process. I'm using OpenSuse 12.1 but I=

've

Quoted 1 line

also tried mounting with a newer kernel 3.2.2 (systemrescue cd) and w=

ith a

Quoted 3 lines

usb-converter connected to another PC without success.
The kernel log seems pretty specific about the crash location, see be=

low.

Quoted 9 lines

Best regards,
Daniel Kuhn
[ =C2=A0 66.476674] ------------[ cut here ]------------
[ =C2=A0 66.476684] kernel BUG at fs/btrfs/free-space-cache.c:1515! [ =C2=A0 66.476691] invalid opcode: 0000 [#1] SMP
[ =C2=A0 66.476699] Modules linked in: tpm_tis tpm tpm_bios i2c_nforc=

e2 serio_raw

Quoted 1 line

pcspkr floppy k10temp asus_atk0110 raid10 raid456 async_raid6_recov a=

sync_pq

Quoted 1 line

raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath li=

near

Quoted 2 lines

ata_generic nouveau ttm drm_kms_helper drm i2c_algo_bit firewire_ohci i2c_core pata_acpi mxm_wmi forcedeth pata_marvell firewire_core pata_=

amd

Quoted 3 lines

video wmi
[ =C2=A0 66.476752]
[ =C2=A0 66.476759] Pid: 1844, comm: mount Not tainted 3.2.2-alt250-i=

586 #2

Quoted 4 lines

System manufacturer System Product Name/M3N-HT DELUXE
[ =C2=A0 66.476772] EIP: 0060:[<c06f7b6f>] EFLAGS: 00010206 CPU: 2 [ =C2=A0 66.476785] EIP is at remove_from_bitmap+0xa8/0x285 [ =C2=A0 66.476792] EAX: 6a92c000 EBX: 00000000 ECX: 0005c000 EDX: 00=

000002

Quoted 1 line

[ =C2=A0 66.476799] ESI: f2f5baa8 EDI: f2f5ba8c EBP: f2f5ba48 ESP: f2=

f5b9ec

Quoted 1 line

[ =C2=A0 66.476805] =C2=A0DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 006=

Quoted 1 line

[ =C2=A0 66.476813] Process mount (pid: 1844, ti=3Df2f5a000 task=3Df2=

ff7080

Quoted 3 lines

task.ti=3Df2f5a000)
[ =C2=A0 66.476818] Stack:
[ =C2=A0 66.476822] =C2=A0f2f5ba2c 00000385 00000000 f2f5ba58 f275037=

0 f2f5ba48

Quoted 2 lines

f2f5ba44 f2f5ba40
[ =C2=A0 66.476837] =C2=A000000019 71bfffff 00000002 71c00000 0000000=

2 f3159600

Quoted 2 lines

073ba000 00000000
[ =C2=A0 66.476851] =C2=A00005c000 00000000 6a92c000 00000002 f2f5baa=

8 00000000

Quoted 3 lines

f2750370 f2f5baa0
[ =C2=A0 66.476865] Call Trace:
[ =C2=A0 66.476877] =C2=A0[<c06f9bf4>] btrfs_remove_free_space+0x34c/=

0x370

Quoted 1 line

[ =C2=A0 66.476889] =C2=A0[<c06bcfa3>] btrfs_alloc_logged_file_extent=

+0x114/0x211

Quoted 4 lines

[ =C2=A0 66.476900] =C2=A0[<c06af00c>] ? btrfs_free_path+0x1b/0x1e [ =C2=A0 66.476909] =C2=A0[<c06af00c>] ? btrfs_free_path+0x1b/0x1e [ =C2=A0 66.476919] =C2=A0[<c06f5afd>] replay_one_extent+0x470/0x5f2 [ =C2=A0 66.476929] =C2=A0[<c050ef9a>] ? __fsnotify_inode_delete+0x8/=

0xa

Quoted 4 lines

[ =C2=A0 66.476941] =C2=A0[<c06f6f55>] replay_one_buffer+0x1d6/0x229 [ =C2=A0 66.476950] =C2=A0[<c06f2cfe>] walk_down_log_tree+0x15b/0x2cd [ =C2=A0 66.476959] =C2=A0[<c06f3062>] walk_log_tree+0x71/0x188 [ =C2=A0 66.476968] =C2=A0[<c06f5011>] btrfs_recover_log_trees+0x24a/=

0x257

Quoted 1 line

[snip]

-o recovery under 3.2 or later should fix it up. You'll want to remain on 3.2 at that point, and then switch to 3.3 when that's released, and so on.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Daniel Kuhn

author

2012-02-11 14:44 UTC #2 lore raw

The mount option "-o recovery" doesn't change anything, the segmentation fault still occurs. Any ideas?

Daniel

Quoted 62 lines · cwillu

Quoted 49 lines · Daniel Kuhn
After a forced power turn-off the filesystem of my primary boot partition cannot be mounted anymore,
btrfs crashes during the mount process. I'm using OpenSuse 12.1 but I've also tried mounting with a newer kernel 3.2.2 (systemrescue cd) and with a usb-converter connected to another PC without success.
The kernel log seems pretty specific about the crash location, see below.
Best regards,
Daniel Kuhn
[   66.476674] ------------[ cut here ]------------
[   66.476684] kernel BUG at fs/btrfs/free-space-cache.c:1515!
[   66.476691] invalid opcode: 0000 [#1] SMP
[   66.476699] Modules linked in: tpm_tis tpm tpm_bios i2c_nforce2 serio_raw
pcspkr floppy k10temp asus_atk0110 raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear ata_generic nouveau ttm drm_kms_helper drm i2c_algo_bit firewire_ohci i2c_core pata_acpi mxm_wmi forcedeth pata_marvell firewire_core pata_amd video wmi
[   66.476752]
[   66.476759] Pid: 1844, comm: mount Not tainted 3.2.2-alt250-i586 #2
System manufacturer System Product Name/M3N-HT DELUXE
[   66.476772] EIP: 0060:[<c06f7b6f>] EFLAGS: 00010206 CPU: 2
[   66.476785] EIP is at remove_from_bitmap+0xa8/0x285
[   66.476792] EAX: 6a92c000 EBX: 00000000 ECX: 0005c000 EDX: 00000002
[   66.476799] ESI: f2f5baa8 EDI: f2f5ba8c EBP: f2f5ba48 ESP: f2f5b9ec
[   66.476805]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   66.476813] Process mount (pid: 1844, ti=f2f5a000 task=f2ff7080
task.ti=f2f5a000)
[   66.476818] Stack:
[   66.476822]  f2f5ba2c 00000385 00000000 f2f5ba58 f2750370 f2f5ba48
f2f5ba44 f2f5ba40
[   66.476837]  00000019 71bfffff 00000002 71c00000 00000002 f3159600
073ba000 00000000
[   66.476851]  0005c000 00000000 6a92c000 00000002 f2f5baa8 00000000
f2750370 f2f5baa0
[   66.476865] Call Trace:
[   66.476877]  [<c06f9bf4>] btrfs_remove_free_space+0x34c/0x370
[   66.476889]  [<c06bcfa3>] btrfs_alloc_logged_file_extent+0x114/0x211
[   66.476900]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476909]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476919]  [<c06f5afd>] replay_one_extent+0x470/0x5f2
[   66.476929]  [<c050ef9a>] ? __fsnotify_inode_delete+0x8/0xa
[   66.476941]  [<c06f6f55>] replay_one_buffer+0x1d6/0x229
[   66.476950]  [<c06f2cfe>] walk_down_log_tree+0x15b/0x2cd
[   66.476959]  [<c06f3062>] walk_log_tree+0x71/0x188
[   66.476968]  [<c06f5011>] btrfs_recover_log_trees+0x24a/0x257
Quoted 2 lines
[snip]
-o recovery under 3.2 or later should fix it up. You'll want to remain on 3.2 at that point, and then switch to 3.3 when that's released, and so on.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Chris Mason

2012-02-13 14:46 UTC #3 lore raw

Quoted 2 lines · Daniel Kuhn

The mount option "-o recovery" doesn't change anything, the segmentation fault still occurs. Any ideas?

Sorry for the hassle, you should be able to get by this by zeroing the log root.

Run btrfs-zero-log /dev/xxx

-chris

Quoted 69 lines

Daniel
Quoted 52 lines · cwillu
Quoted 49 lines · Daniel Kuhn
After a forced power turn-off the filesystem of my primary boot partition cannot be mounted anymore,
btrfs crashes during the mount process. I'm using OpenSuse 12.1 but I've also tried mounting with a newer kernel 3.2.2 (systemrescue cd) and with a usb-converter connected to another PC without success.
The kernel log seems pretty specific about the crash location, see below.
Best regards,
Daniel Kuhn
[   66.476674] ------------[ cut here ]------------
[   66.476684] kernel BUG at fs/btrfs/free-space-cache.c:1515!
[   66.476691] invalid opcode: 0000 [#1] SMP
[   66.476699] Modules linked in: tpm_tis tpm tpm_bios i2c_nforce2 serio_raw
pcspkr floppy k10temp asus_atk0110 raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear ata_generic nouveau ttm drm_kms_helper drm i2c_algo_bit firewire_ohci i2c_core pata_acpi mxm_wmi forcedeth pata_marvell firewire_core pata_amd video wmi
[   66.476752]
[   66.476759] Pid: 1844, comm: mount Not tainted 3.2.2-alt250-i586 #2
System manufacturer System Product Name/M3N-HT DELUXE
[   66.476772] EIP: 0060:[<c06f7b6f>] EFLAGS: 00010206 CPU: 2
[   66.476785] EIP is at remove_from_bitmap+0xa8/0x285
[   66.476792] EAX: 6a92c000 EBX: 00000000 ECX: 0005c000 EDX: 00000002
[   66.476799] ESI: f2f5baa8 EDI: f2f5ba8c EBP: f2f5ba48 ESP: f2f5b9ec
[   66.476805]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   66.476813] Process mount (pid: 1844, ti=f2f5a000 task=f2ff7080
task.ti=f2f5a000)
[   66.476818] Stack:
[   66.476822]  f2f5ba2c 00000385 00000000 f2f5ba58 f2750370 f2f5ba48
f2f5ba44 f2f5ba40
[   66.476837]  00000019 71bfffff 00000002 71c00000 00000002 f3159600
073ba000 00000000
[   66.476851]  0005c000 00000000 6a92c000 00000002 f2f5baa8 00000000
f2750370 f2f5baa0
[   66.476865] Call Trace:
[   66.476877]  [<c06f9bf4>] btrfs_remove_free_space+0x34c/0x370
[   66.476889]  [<c06bcfa3>] btrfs_alloc_logged_file_extent+0x114/0x211
[   66.476900]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476909]  [<c06af00c>] ? btrfs_free_path+0x1b/0x1e
[   66.476919]  [<c06f5afd>] replay_one_extent+0x470/0x5f2
[   66.476929]  [<c050ef9a>] ? __fsnotify_inode_delete+0x8/0xa
[   66.476941]  [<c06f6f55>] replay_one_buffer+0x1d6/0x229
[   66.476950]  [<c06f2cfe>] walk_down_log_tree+0x15b/0x2cd
[   66.476959]  [<c06f3062>] walk_log_tree+0x71/0x188
[   66.476968]  [<c06f5011>] btrfs_recover_log_trees+0x24a/0x257
Quoted 1 line
[snip]
Quoted 7 lines
-o recovery under 3.2 or later should fix it up. You'll want to remain on 3.2 at that point, and then switch to 3.3 when that's released, and so on.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html