[systemd-devel] fstab, rootfs on btrfs

[Chris Murphy]

On Nov 27, 2013, at 4:53 AM, Kay Sievers <kay at vrfy.org> wrote:

> On Wed, Nov 27, 2013 at 5:16 AM, Chris Murphy <lists at colorremedies.com> wrote:
>> 
>> In Fedora 20, by default anaconda sets fs_passno in fstab to 1 for / on btrfs. During offline updates, this is causing systemd-fstab-generator to freak out not finding fsck.btrfs.
>> 
>> https://bugzilla.redhat.com/show_bug.cgi?id=1034563
> 
> Right, it should not set 1 for btrfs.

Since it can be mounted rw from the get go, is it going to far to plan for one day dropping the initial ro mount, remount rw sequence?

Today it already works to set the bootloader kernel parameter to mount btrfs rw from the start, and remove the rootfs fstab entry entirely.

>> It doesn't seem to me that for file systems that don't require an fs check, that fstab should indicate it does require an fs check, just to inhibit hissy fits by other processes not liking that the device is missing. But maybe I'm missing something.
> 
> Such hacks are plain wrong and not needed for today's systems.

That's what what I was hoping to hear, thanks.


Chris Murphy