- 2.0 Btrfs driver. I've tested this driver with a simple one-partition
- filesystem and with a filesystem that spans two physical devices
- (although I've made no attempt to ensure that the driver can actually
- read files written to both devices). Samuel Liao has used the driver
- with a compressed Btrfs volume. The driver will handle subvolumes, but
- you may need to add kernel options if you're booting a Linux kernel
- directly from a filesystem that uses subvolumes. For instance, on a
- test installation of Ubuntu 14.04 alpha on such a system, I needed to
- set <tt>also_scan_dirs + @/boot</tt> in <tt>refind.conf</tt> and add
- <tt>rootflags=subvol=@</tt> to the kernel options in my
- <tt>refind_linux.conf</tt> file. Without the first of these options,
- rEFInd could not locate my kernel; and without the second, the boot
- failed with a message to the effect that the initial RAM disk could not
- find <tt>/sbin/init</tt>. rEFInd 0.10.0 adds <tt>@/boot</tt> as a
- standard option to <tt>also_scan_dirs</tt>, and its
- <tt>refind-install</tt> and <tt>mkrlconf</tt> scripts should pick up
- the root flags, assuming the system is booted into the regular
- installation. These additions make it easier to set up rEFInd to work
- with Btrfs.</li>
+ 2.0 Btrfs driver. I've tested this driver with simple one-partition
+ filesystems on several installations, and with a filesystem that spans
+ two physical devices on one (although I've made no attempt to ensure
+ that the driver can actually read files written to both devices). Samuel
+ Liao has used the driver with a compressed Btrfs volume. The driver will
+ handle subvolumes, but you may need to add kernel options if you're
+ booting a Linux kernel directly from a filesystem that uses subvolumes.
+ For instance, when booting Ubuntu from Btrfs, <tt>also_scan_dirs +
+ @/boot</tt> must be set in <tt>refind.conf</tt> and
+ <tt>rootflags=subvol=@</tt> must be added to the kernel options in
+ <tt>refind_linux.conf</tt>. Without the first of these options, rEFInd
+ can not locate the kernel; and without the second, the boot fails with a
+ message to the effect that the initial RAM disk could not find
+ <tt>/sbin/init</tt>. rEFInd 0.10.0 adds <tt>@/boot</tt> as a standard
+ option to <tt>also_scan_dirs</tt>, and its <tt>refind-install</tt> and
+ <tt>mkrlconf</tt> scripts should pick up the root flags, assuming the
+ system is booted into the regular installation. These additions make it
+ easier to set up rEFInd to work with Btrfs.</li>