btrfsck SIGSEGVs in find_first_block_group
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | btrfs-tools (Ubuntu) |
Medium
|
Surbhi Palande | ||
Bug Description
Binary package hint: btrfs-tools
A follow on bug from bug #601874.
After boot, the first time I run btrfsck it crashes with bug #601874. The second time I run it, it crashes in find_first_
It sometimes also dies with an abort. I haven't yet got a backtrace for that; I'll file another bug when I do.
Backtrace attached.
Related branches
- Colin Watson: Needs Fixing on 2010-08-18
-
Diff: 44 lines (+23/-1)3 files modifieddebian/changelog (+8/-1)
debian/patches/04-fix-601874.patch (+14/-0)
debian/patches/series (+1/-0)
| Chris Halse Rogers (raof) wrote : | #1 |
| Changed in btrfs-tools (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in btrfs-tools (Ubuntu): | |
| assignee: | nobody → Surbhi Palande (csurbhi) |
| Changed in btrfs-tools (Ubuntu): | |
| status: | Confirmed → In Progress |
| Chris Halse Rogers (raof) wrote : Re: [Bug 601877] Re: btrfsck SIGSEGVs in find_first_block_group | #2 |
| Surbhi Palande (csurbhi) wrote : | #4 |
Hi Chris Halse Rogers,
Thanks a lot for your consideration and help :) I have kept a test ppa of btrfs-tools at https:/
Can you please let me know if this fixes things for you? I am not able to reproduce the same bug here.
| Chris Halse Rogers (raof) wrote : | #5 |
Well, it no longer segfaults. It now aborts in btrfs_lookup_
Backtrace attached.
| Chris Halse Rogers (raof) wrote : | #6 |
I'd love to give you a btrfs image, but that segfaults; backtrace attached.
| Surbhi Palande (csurbhi) wrote : | #7 |
Chris Halse Rogers, did you have a system crash or had to force poweroff your machine? In that case, by any chance do you have the dmesg/kernel log of the crash and/or first boot after the crash?
| Chris Halse Rogers (raof) wrote : | #8 |
*giggle*.
Sorry - I've had to uncleanly kill this machine quite frequently, for a variety of reasons (most of which to do with X). I don't have those logs that far back.
I could possibly play around with powering off my machine while under IO load if that would be helpful.
| Surbhi Palande (csurbhi) wrote : | #9 |
I guess, btrfs aborting due to a corrupted fs is expected behavior as of now. I think, a safe way is to take snapshots regularly of your btrfs and then reverting back to the previous snapshots when something goes wrong. I will also find out more on this and update here if I do find out something more.
I guess you'd probably like me to keep this disc image around for
testing fixes or hypotheses.
I'd like to replace it with a filesystem less broken, but btrfs-image
*also* segfaults with similar messages, so I'll keep this filesystem
around until you tell me it's no longer going to be useful :).