docker btrfs - kernel panic <SOLVED>

[ez2002]

All:

I have been getting this kernel panic related to btrfs (assuming Docker is the only using this file system?).

 

Trying to reboot the system now as the web GUI is completely froze/unreachable.

 

Unraid v6.1.9

 

------------[ cut here ]------------

kernel BUG at fs/btrfs/ctree.h:2578!

invalid opcode: 0000 [#1] PREEMPT SMP

Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables kvm_amd kvm vhost_net vhost macvtap macvlan tun md_mod k10temp i2c_piix4 pata_atiixp e1000e ahci libahci tg3 ptp pps_core acpi_cpufreq

CPU: 1 PID: 29749 Comm: btrfs-transacti Not tainted 4.1.18-unRAID #1

Hardware name: HP ProLiant MicroServerr, BIOS O41    07/29/2011

task: ffff88007b9be480 ti: ffff8803f8fbc000 task.ti: ffff8803f8fbc000

RIP: 0010:[<ffffffff8129392b>]  [<ffffffff8129392b>] lookup_inline_extent_backref+0x1bb/0x524

RSP: 0018:ffff8803f8fbfa98  EFLAGS: 00010297

RAX: 0000000000000090 RBX: ffff8802748f55a0 RCX: ffff8802b4a70000

RDX: 0000000000003000 RSI: ffff880000000000 RDI: ffff8800d8ab69d8

RBP: ffff8803f8fbfb38 R08: 0000000000004000 R09: ffff8803f8fbfa50

R10: 0000000000000003 R11: 000000000000381b R12: 0000000000000090

R13: 000000000000379d R14: 000000000000381a R15: ffff8800d8ab69d8

FS:  00002ad54b604700(0000) GS:ffff88041fc80000(0000) knlGS:0000000000000000

CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b

CR2: 00000000027beb74 CR3: 00000000d07b1000 CR4: 00000000000006e0

Stack:

ffff8803f8fbfbd8 0000000000000850 ffff8803f8fbfac8 0000000000003823

0000000037d2c000 ffff8803e2a57800 0000000000000021 000000b0ffffffff

ffff88040ce79e40 c0008803e76461f0 00a90000000037d2 0000000000000000

Call Trace:

[<ffffffff812963fd>] __btrfs_free_extent+0x140/0x8dc

[<ffffffff81292084>] ? block_group_cache_tree_search+0xb7/0xc6

[<ffffffff8129c585>] __btrfs_run_delayed_refs+0x9ce/0xd3a

[<ffffffff8100a4a9>] ? __switch_to+0x43c/0x4c8

[<ffffffff8129e77c>] btrfs_run_delayed_refs+0x69/0x21c

[<ffffffff812acbf2>] btrfs_commit_transaction+0x47/0xa81

[<ffffffff812ad996>] ? start_transaction+0x36a/0x496

[<ffffffff810829f9>] ? __internal_add_timer+0xb5/0xb5

[<ffffffff812a93ce>] transaction_kthread+0xfa/0x1cb

[<ffffffff812a92d4>] ? btrfs_cleanup_transaction+0x461/0x461

[<ffffffff8105c74a>] kthread+0xd6/0xde

[<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

[<ffffffff815f7f12>] ret_from_fork+0x42/0x70

[<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172

Code: 94 c6 84 c0 74 27 45 84 f6 0f 85 6d 03 00 00 be 0c 06 00 00 48 c7 c7 bc 22 76 81 41 bf fb ff ff ff e8 fe 3e db ff e9 00 01 00 00 <0f> 0b 48 63 73 40 31 c9 ba 15 00 00 00 4c 8b 3b 48 6b f6 19 4c

RIP  [<ffffffff8129392b>] lookup_inline_extent_backref+0x1bb/0x524

RSP <ffff8803f8fbfa98>

---[ end trace b375fec2ca735b86 ]---

 

Thanks

 

[RobJ]

Well if it's Docker, you have it much easier than others with BTRFS issues.  Just remove docker.img and recreate it, then add back your templates (Community Apps makes that easy).

[ez2002]

Thanks.

I did that last night and it seems to be stable now.

edit the docker.cfg so it will not auto start. Restart, and then delete the img and btrfs folder manually.

then recreate it again.