btrfs file system crashes with kernel BUG at /build/buildd/linux-3.5.0/fs/btrfs/inode.c:3758!

Bug #1022374 reported by miked
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Rolf Leggewie

Bug Description

[6.42`] sda: sda1 sda2 < sda5 >
[9.432`] Btrfs loaded
[9.459`] device fsid 55bf9175` devid 1 transid 1094 /dev/sda1
[14.632`] device fsid 55bf9175` devid 1 transid 1094 /dev/disk/by-uuid/55bf9175`
[14.634`] btrfs: disk space caching is enabled
[14.690`] btrfs: bdev /dev/disk/by-uuid/55bf9175` errs: wr 0, rd 0, flush 0, corrupt 0, gen 0
[14.80864`] ----------------------[cut here]-------------------------
[14.80867`] kernel BUG at /build/build/linux-3.5.0/fs/btrfs/inode.c:3758!
[14.80869`] invalid opcode: 0000 [#1] SMP
[14.8087`] Modules linked in: btrfs zlib_deflate libcrc32c hid_generic nouveau usbhid ttm drm_kms_helper drm hid firewire_ohci firewire_core i2c_algo_bit mxm_wmi 3c59x crc_itu_t video wmi floppy
[14.8088`]
[14.80891`] Pid:248, comm: exe Not tainted 3.5.0-3 generic #3-Ubuntu Dell Computer Corporation Precision Workstation 530 MT /
[14.80896`] EIP: 0060:[<e0c03a0f>] EFLAGS: 00010246 CPU: 0
[14.80903`] EIP is at btrfs_evict_inode+0x10f/0x310 [btrfs]
[14.80905`] EAX: 00000000 EBX: df471000 ECX: 7fffffff EDX: da62fabc
[14.80909`] ESI: df03da70 EDI: df03d9d4 EBP: da62fb34 ESP: da62fb04
[14.80913`] DS: 007b ES: 007b FS:00d8 GS: 00e0 SS: 0068
[14.80916`] CRO: 8005003b CR2:b76e0000 CR3: 1a5b0000 CR4: 000007f0
[14.8092`] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[14.80923`] DR6: ffff0ff0 DR7: 00000400
[14.80927`] Process exe (pid:248, ti=da62e000 task=da5e32c0 task.ti=da62e000)
[14.80932`] Stack:
[14.80935`] ffffffff ffffffff c1065250 da62fb10 da62fb10 df03da28 df03d9d4 00001000
[14.8094`] 00001000 df03d9d4 df03da70 e0c57120 da62fb48 c1165ea6 df03d9d4 df03da28
[14.8095`] da73f400 da62fb60 c1166050 00000000 df040000 df471000 df03d9d4 da62fba8
[14.8096`] Call Trace:
[14.80970`] [<c1065250>] ? autoremove_wake_function+0x50/x50
[14.80974`] [<c1165ea6>] evict+0x96/0x170
[14.80978] [<c1166050>] iput+0xd0/0x1c0
[14.8098`] [<e0c36ca2>] fixup_inode_link_counts+0xf2/0x160 [btrfs]
[14.80991`] [<e0c381f3>] btrfs_recover_log_trees+0x203/0x370 [btrfs]
[14.80997`] [<e0c36d10>] ? fixup_inode_link_counts+0x160/0x160 [btrfs]
[14.81004`] [<e0bf6a34>] open_ctree+0x13a4/0x1920 [btrfs]
[14.81008`] [<c12c4be9>] ? strlcpy+0x39/0x50
[14.81013`] [<e0bd284e>] btrfs_mount+0x890 [btrfs]

o.k., there's more but you get the idea. I can put more if helpful.
there is about 19 more lines.

Revision history for this message
miked (miked11) wrote :

This bug takes out your system start-up. Recovery did not help, nor did using previous kernel builds. Not a good thing for a newly announced file-system. Please let me know how to proceed. What are my options, is it fix-able, or does it require a re-install. I was getting a sparse file error before this latest bug, and tried a few fixes, which gave me record fail errors. this bug appeared after leaving my system unattended, and was on the screen when I returned. It is now the only thing that appears on the screen after reboot. Today even less appears. It boots to BusyBox v1.19.3 (Ubuntu1:1.19-3-7ubuntu1) (initramfs).

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Ubuntu has not shipped a btrfs package for a long time, moving to generic Ubuntu for triage.

This bug is pretty old. Did anyone affected by this experience it with trusty or later?

btrfs in 2012 was highly experimental and clearly not meant for ordinary use.

affects: btrfs (Ubuntu) → ubuntu
Changed in ubuntu:
assignee: nobody → Rolf Leggewie (r0lf)
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.