Fresh Bluefin install in degraded mode: btrfs compress parameters not applied

[ijanos]

I noticed that a fresh Bluefin install is in degraded mode.

❯ systemctl is-system-running 
degraded

❯ systemctl --failed
  UNIT                       LOAD   ACTIVE SUB    DESCRIPTION                         
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

1 loaded units listed.

Looks like /etc/fstab parameters are ignored, and the btrfs filesystem is not mounted without compress parameters. Notice compress=zstd:1 is present in fstab but not present in the output of the mount command.

I think this is an ostree upstream issue, but I couldn't find this referenced in the bug tracker. Is this known? There is a workaround discussed in the linked tickets and I wonder what is bluefin's stance on implementing it.

https://discussion.fedoraproject.org/t/talk-mount-options-are-ignored-in-fedora-atomic-desktops-42/148874

https://gitlab.com/fedora/ostree/sig/-/issues/72

❯ cat /etc/fstab 

#
# /etc/fstab
# Created by anaconda on Sun Dec 28 13:10:16 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
# Updated by bootc-fstab-edit.service
UUID=fe088622-bc6f-418b-ad73-9ae1b02268f1 / btrfs subvol=root,compress=zstd:1,ro 0 0
UUID=ac5591fb-fa14-4c5e-965f-cb53e183b6d4 /boot ext4 defaults 1 2
UUID=AE69-D9B7 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=fe088622-bc6f-418b-ad73-9ae1b02268f1 /home btrfs subvol=home,compress=zstd:1 0 0
UUID=fe088622-bc6f-418b-ad73-9ae1b02268f1 /var btrfs subvol=var,compress=zstd:1 0 0

❯ mount | grep btrfs
/dev/nvme0n1p3 on /etc type btrfs (rw,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/root)
/dev/nvme0n1p3 on /sysroot type btrfs (ro,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/root)
/dev/nvme0n1p3 on /sysroot/ostree/deploy/default/var type btrfs (rw,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/root)
/dev/nvme0n1p3 on /var type btrfs (rw,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/var)
/dev/nvme0n1p3 on /var/home type btrfs (rw,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/home)

[castrojo]

We know about this, I'm mostly just waiting to see what the upstream team tells us to do, I'll add this to their weekly team meeting when they start up again, thanks!

[andrew22224]

Any further updates on this?

[m2Giles]

You can comment out the entry for / in /etc/fstab.

This is a function of the switch to composefs and there being machine specific state inside of /etc.

[andrew22224]

So I should comment out all lines related to my drive where I don't see the compress section?

[andrew22224]

Didn't fix the issue I commented out the root mount on my fstab with no luck.