Red Hat Bugzilla – Bug 821212
btrfs-convert segfault on lv_root
Last modified: 2013-07-31 21:28:47 EDT
Description of problem:
btrfs-convert segfaults when converting lv_root from ext4 to btrfs.
Version-Release number of selected component (if applicable):
2 for 2
Steps to Reproduce:
1. Install F17 Live Desktop with all defaults
3. Firstboot, create first user...
4. Reboot Live Desktop media
5. btrfs-convert lv_home no errors.
6. btrfs-convert lv_root failure.
segfault on conversion
filesystem appears trashed, not bootable, not sure how to recover or if recovery is possible
Conversion to btrfs, or graceful failure.
ABRT says the backtrace is unusable so it wouldn't file this automatically. What I have now is /var/log/messages, the segfault ccpp folder contents, and dmesg.
Hardware is EFI booted Macbook Pro.
Created attachment 584106 [details]
abrt ccpp folder files
Created attachment 584107 [details]
Created attachment 584108 [details]
Created attachment 584110 [details]
panic screen upon mounting
I get a panic when mounting with or without -o recovery.
Presently the work around appears to be btrfs-convert -r which does roll back successfully, and the volume can then be mounted again as ext4.
To be clear, I'm using btrfs-convert from Live Desktop on an ext4 lv_root which is not mounted, but was created with the same Live Desktop.
3 for 4 reproducibility.
If after installation of F17, I do not reboot off the installed HDD, but rather immediately reboot off Live Desktop install media, (i.e. the F17 on disk has not been modified in any way by virtue of booting, running firstboot, launching any apps etc), the problem does NOT occur.
If I run through first boot, launch Fire Fox, then reboot off Live Desktop installation media, lv_home converts to btrfs OK. But I get a segmentation fault when doing it on lv_root.
Can you tell me what versions of libuuid and e2fsprogs you have on there so I can get the right debuginfo installed, it seems to be blowing up somewhere in libuuid and I can't tell where.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.