I'm using a F13 Beta RC4 with a root filesystem formated as btrfs
inside a LVM and i have not seen any problems yet.
I've just use the manual partitionning because my partitions and LVM
was already created my a previous install.
Hoping it will help you to know BTRFS already works well inside LVM on
some F13 installs.
2010/4/8 Michael Cronenworth <mike(a)cchtml.com>:
I installed F13 beta RC4 with all the defaults, except I installed
on
two Intel SSDs (40gig G2 drives) in a Linux software RAID1
configuration. I left anaconda to install /boot to ext4 and / to an LVM
with ext4 and a swap area inside of it. The benchmark results from
palimpset show me maxing out my SATA 2 links. :)
I rebooted into a F13 beta RC4 live USB drive and ran "btrfs-convert
/dev/mapper/vg_foo-LogVol00" and it converted successfully. I updated my
/etc/fstab from "ext4" to "btrfs" as the root file system. Upon
rebooting I was met with a failure of setting the hostname (odd) and
then iptables complained of missing library files and 90% of the default
services failed to start. The init failed to kick off TTYs and the X
server so I was not given a login. I can hit CTRL+ALT+DEL and reboot,
however.
I entered into the live image again and set back fstab to "ext4" and
rebooted. I was presented with a rescue boot prompt and gave it the root
password. From there I changed my fstab to "btrfs" and typed
"reboot"
and Fedora continued to successfully boot (without physically rebooting)
and I am typing this message from the install while the rootfs is btrfs.
If I were to reboot right now, Fedora would not come back up and would
result in the same service start-up failures. I would have to repeat my
hack of setting fstab back to "ext4".
What am I missing from having a working btrfs system? Or is this a bug?
Thanks,
Michael
--
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test