Red Hat Bugzilla – Bug 832326
partitioning fails when using kickstart and btrfs
Last modified: 2013-07-31 14:26:52 EDT
Created attachment 592061 [details]
The video of the crash
Description of problem:
I can't use btrfs while partitioning 7 GB drive.
Version-Release number of selected component (if applicable):
Try using a kickstart that contains the following lines:
clearpart --all --initlabel --drives=/dev/sda
bootloader --location=mbr --timeout=5 --driveorder=sda --append="rhgb quiet acpi=force audit=1 elevator=deadline"
part biosboot --fstype=biosboot --size=1 --ondisk=sda
part /boot --fstype=ext4 --size=500 --ondisk=sda
part / --fstype=btrfs --fsoptions="ssd,noatime,ssd,compress=lzo,autodefrag,space_cache" --grow --ondisk=sda --label=f17_root
It fails saying:
An error occurred mounting device /dev/sda3 as /: filesystem has not been created. This is a fatal error and the install cannot continue.
It should just work.
I have a video; which I will attach. Also, this same kickstart works fine on Fedora 16.
Please attach /tmp/anaconda.log, /tmp/syslog, and /tmp/storage.log to this bug report. Thanks.
The syntax for creating BTRFS volumes is more complex now to support the many advanced features of BTRFS:
I can confirm it works ok with:
part biosboot --fstype biosboot --size 1
part /boot --fstype="ext4" --ondisk=sda --size=512
part swap --fstype="swap" --ondisk=sda --size=2048
part btrfs.01 --fstype btrfs --grow --ondisk=sda --size=1
btrfs none --label=FEDORA btrfs.01
btrfs / --subvol --name=root LABEL=FEDORA
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.