Bug 1112697
| Summary: | RFE: allow to override default fs type for autopart | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Stancek <jstancek> | ||||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.1 | CC: | atodorov, bcl, blc, eguan, jburke, jstancek, mbanas, pbunyan, swhiteho | ||||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | anaconda-19.31.105-1 | Doc Type: | Enhancement | ||||||
| Doc Text: |
Feature:
Add the ability to specify the filesystem type when using the kickstart autopart command.
Reason:
More flexibility in auto-partitioning installations.
Result:
The kickstart autopart command now supports the --fstype= option allowing the user to select any of the supported filesystems as the one to use when autopartition the system.
Note that btrfs is not a fstype and is selected as before, with autopart --type=btrfs
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1129912 (view as bug list) | Environment: | |||||||
| Last Closed: | 2015-03-05 14:01:34 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1129912 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jan Stancek
2014-06-24 13:55:20 UTC
Created attachment 933388 [details]
storage.log --fstype=ext4, RHEL-7.1-20140828.n.0
On RHEL-7.1-20140828.n.0 with --fstype=ext4 all volumes are ext4 except the /boot, which is still xfs:
zerombr
clearpart --all --initlabel
autopart --fstype=ext4
# df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/rhel_dell--pet20--01-root ext4 50G 1.7G 45G 4% /
devtmpfs devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 1.9G 8.5M 1.8G 1% /run
tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/sda1 xfs 494M 111M 383M 23% /boot
/dev/mapper/rhel_dell--pet20--01-home ext4 864G 77M 820G 1% /home
# yum info -q anaconda
Available Packages
Name : anaconda
Arch : x86_64
Version : 19.31.85
Release : 1.el7
...
# yum info -q pykickstart
Available Packages
Name : pykickstart
Arch : noarch
Version : 1.99.43.12
Attached is storage.log from installation.
This should be fixed, I'd expect all default partitions to be the same type. Created attachment 952356 [details]
Patch to fix fstype on /boot
Give this updates.img a try against anaconda-19.31.104-1
(In reply to bcl from comment #5) > Created attachment 952356 [details] > Patch to fix fstype on /boot > > Give this updates.img a try against anaconda-19.31.104-1 autopart --fstype=ext4 -> OK, lvm volumes and /boot are ext4 autopart --fstype=xfs -> OK, lvm volumes and /boot are xfs autopart --fstype=btrfs -> failed with "btrfs is not valid fstype, use --type=btrfs instead", I was expecting "--fstype=btrfs --type=lvm" to be supported, where --type=lvm is default partitioning scheme. (In reply to Jan Stancek from comment #7) > (In reply to bcl from comment #5) > > Created attachment 952356 [details] > > Patch to fix fstype on /boot > > > > Give this updates.img a try against anaconda-19.31.104-1 > > autopart --fstype=ext4 -> OK, lvm volumes and /boot are ext4 > autopart --fstype=xfs -> OK, lvm volumes and /boot are xfs > autopart --fstype=btrfs -> failed with "btrfs is not valid fstype, use > --type=btrfs instead", I was expecting "--fstype=btrfs --type=lvm" to be > supported, where --type=lvm is default partitioning scheme. That's expected. btrfs is both a filesystem and a volume manager, it was already supported using --type. You can't use lvm and btrfs at the same time. RE: comment #8 It is possible to use btrfs with LVM rather than using its own internal volume management, and I think it is something that we should support. Maybe this is not the right place to raise that issue, but longer term we should allow for both set ups. (In reply to Steve Whitehouse from comment #9) > RE: comment #8 > > It is possible to use btrfs with LVM rather than using its own internal > volume management, and I think it is something that we should support. Maybe > this is not the right place to raise that issue, but longer term we should > allow for both set ups. That's outside the scope of this bug. You would need to file RFEs with python-blivet to implement it and with Anaconda to support it with a good description of why you think it needs to be supported. Moving to VERIFIED, see comment #8. Please open RFEs for using btfs with LVM volume management as described in comment #10. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0312.html |