F43 wakes up with readonly root fs after sleep

Ask Fedora
, ,
1

Hi folks,

I am very happy fedora user and also have some btrfs exporiense last ocuple of years.
Got laptop that under ext4 on root runs great but desided to re-install with raid on 2 nvmes and by default if got btrfs. My issue is most of the times I wake up laptop it is with read only root fs and there is not much to do. Issue is with how sleep and BTRFS are handled imho.
Any ideas for sorting this out are more than welcomed !
Here is some check of FS and it looks great:
bahur@invicta:~$ sudo btrfs check --force /dev/dm-1
[sudo] password for bahur:
Opening filesystem to check…
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/dm-1
UUID: 4ccd1f7e-9c12-4f5f-b57a-a4fbd65042c8
[1/8] checking log
[2/8] checking root items
[3/8] checking extents
[4/8] checking free space tree
[5/8] checking fs roots
[6/8] checking only csums items (without verifying data)
[7/8] checking root refs
[8/8] checking quota groups skipped (not enabled on this FS)
found 280862552064 bytes used, no error found
total csum bytes: 254804992
total tree bytes: 555089920
total fs tree bytes: 255606784
total extent tree bytes: 21463040
btree space waste bytes: 63777972
file data blocks allocated: 7678780096512
referenced 284745400320

Cheers
Teo

2

We need to see a complete dmesg or journalctl -k to figure out what’s going on, why it’s going read-only.

bahur@invicta:~$ sudo btrfs check --force /dev/dm-1
Opening filesystem to check…
WARNING: filesystem mounted, continuing because of --force

For what it’s worth, I do not recommend using –force on a mounted Btrfs. The results are not reliable except if it comes up clean, as it did here. Best to run the btrfs check in the initramfs (you can drop to the initramfs with boot parameter rd.break=pre-mount) or a LiveISO imaged to a USB stick and booting from the USB stick.

1 Like
3

Thanks for the answer, moved to CentOS 10 and disabled power management