Bug 571910
| Summary: | installation fails at kickstart option --fstype="btrfs" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matej Nemcek <ybdaba> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | anaconda-maint-list, jonathan, valent.turkovic, vanmeeuwen+fedora, vedran |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-03-10 04:58:20 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Matej Nemcek
2010-03-09 20:08:09 UTC
The error messages you're getting don't really have anything to do with --fstype=btrfs. It's telling you that you're trying to install too much stuff into too small of a partition. What happens if you either increase the size of / or decrease the number of packages you're installing? The only way this would have something to do with --fstype=btrfs is if you change it to --fstype=ext4 and it works. Well, that partition is 7GB. I think it's enough at minimal installation. Yes, with --fstype=ext4 installation works from kickstart. Is --fstype=btrfs officially supported? Or how to install system root at btrfs from kickstart? part / --fstype="btrfs" --size=4000 makes a partition that's 4 GB, not 7 GB. Which are you actually doing? Please attach your complete kickstart file to this bug report. btrfs is supported as long as you provide the "btrfs" command line option, as it's not quite ready for mainstream use yet. I just wanna say, that I raised to --size=7000, but I recieve same error. firewall --enabled --ssh install cdrom repo --name=my-everything --mirrorlist=http://mirrors.fedoraproject.org/metalink?repo=fedora-13-Alpha&arch=i386 repo --name=my-updates --mirrorlist=http://mirrors.fedoraproject.org/metalink?repo=updates-testing-f13-Alpha&arch=i386 rootpw --iscrypted $1$tZ8uWXUF$lJm8YB9z/pTHFBA7.HpUV/ auth --useshadow --passalgo=sha512 text keyboard us lang en_US selinux --disabled skipx logging --level=info reboot timezone Etc/GMT+1 bootloader --location=mbr zerombr clearpart --all part /boot --fstype="ext4" --size=200 part swap --fstype="swap" --size=256 part / --fstype="btrfs" --size=7000 But tell me, how to use proper btrfs option in kickstart? As I previously stated: btrfs is supported as long as you provide the "btrfs" command line option, as it's not quite ready for mainstream use yet. Did you make sure to add that as an option when you booted anaconda? Oh, I'm blind today. Also, should be included btrfs option as experimental at http://fedoraproject.org/wiki/Anaconda/Options Installation sucess. Thanks. Great, glad it's working out for you. Thanks for retesting. Setting up a separate /boot partition is essential because if you just switch / partition from ext4 to btrfs you get an error. Btrfs doesn't support booting from it. Also hope this blog post helps: http://kernelreloaded.blog385.com/index.php/archives/btrfs-fedora-remix/ Could anybody give an example of working kickstart file that creates brtfs livecd iso image? I tried few examples and they all create only ext3 iso images :( Here is what I tried: part /boot –size=128 –onpart=sda1 –fstype=ext3 part pv.01 –size=128 –onpart=sda2 –grow volgroup VolGroup pv.01 logvol / –size=128 –vgname=VolGroup –fstype=btrfs –grow –name=root –fsoptions=ssd and more simple one: part /boot --size 120 --fstype ext4 part / --size 6000 --fstype="btrfs" bootloader --location=mbr --append=btrfs None of these options create btrfs iso image. Any idea why? Should I clone this bug as a new one or will this one be reopened? You'd need to ask the livecd-tools people that. We're not responsible for that code. |