Fortunately, this is how it already works, as far as I know. The
installer will not create btrfs filesystems in automatic partitioning,
and if you try to use btrfs on /boot (or on / without a separate /boot)
then it will raise an error. Here are the templates for the two error
messages in questio
Fortunately, I was aware I needed a separate /boot and didn't hit that
particular trap.
But for as long as booting from btrfs is unsupported, it would make
sense for the installer to detect this and either create its own /boot
in automated mode, or when manually partitioning, prevent the user from
I've uploaded 1.99~20101124-1ubuntu1 to Natty, fixing this bug.
grub2 (1.99~20101122-1) experimental; urgency=low
[ Colin Watson ]
* New Bazaar snapshot. Too many changes to list in full, but some of the
more user-visible ones are as follows:
[...]
- Basic btrfs detection/UUID su
You can't use btrfs for /boot yet - you must have a separate /boot if
you're using btrfs on /. This is not the same as this bug, but we are
aware of it and indeed have posted patches. It's currently held up on
licence conflicts, although we are trying to resolve them.
--
When selecting btrfs fo
This seems to affect me, too.
I installed Kubuntu 10.10 using btrfs as / and ext4 as /boot. Everything
worked fine until i decided to back everything up and change my / so it
has one "rootfs" subvolume (which i made as the default one) to be able
to create snapshots of the whole system.
Since tha
Thanks for your report. This will be fixed with the next GRUB upstream
snapshot, which I'll be uploading to Natty as soon as I've got a few
more build issues sorted out:
2010-09-09 Robert Millan
Basic Btrfs support (detection and UUID).
* grub-core/fs/btrfs.c: New file.
