Red Hat Bugzilla – Bug 891443
crash when reusing existing Btrfs volume
Last modified: 2013-12-25 11:28:32 EST
Description of problem:
When using an existing Btrfs volume, a new root subvolume is required. When creating new Root subvol, anaconda crashes at the start of installation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Btrfs volume, single disk.
2. Manual Partitioning.
3. Create new mount point Root.
4. Finish Partitioning
5. Begin Installation
In the simple case above, no existing subvols exist or are reused so reformatting the file system is a viable work around; in the practical case I'd like to reuse an existing home and/or boot subvol in which case reformat isn't possible, and always results in a crash, no work around.
Created attachment 671762 [details]
Created attachment 671763 [details]
Created attachment 671764 [details]
Created attachment 671765 [details]
Created attachment 671766 [details]
libreport reports the exact same error message, and considers this bug a dup of bug 872739, which was also a blocker, possibly for different reasons.
Proposing as blocker:
F18 Beta Release Criterion #10: The installer's custom partitioning mode must be cable of creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types and reject obviously invalid operations without crashing.
If this bug isn't fixed, it won't be possible to install to an existing Btrfs file system without a reformat, which means nuking the user's home even if its on its own subvolume.
Fix pushed to master and f18-branch. Next build will include it.
Discussed at 2012-01-03 go/no-go meeting: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-01-03/f18_final_gono-go_meeting.2013-01-03-17.01.log.txt . Accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following: Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types"
anaconda-18.37.9-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.37.9-1.fc18 fixes this bug.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.37.9-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.37.10-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.37.11-1.fc18 has been submitted as an update for Fedora 18.
Still fixed in anaconda-18.37.11-1.fc18.
anaconda-18.37.11-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.