getting rid of /var not unmounted at reboot/shutdown

English Install/Boot/Login
1

Greetings !!

Is that a good idea to remove the /var btrfs sub volume from fstab after have copied it on the root folder (/) ?

mv /var /varcopy 
unmount /var
<change fstab: remove /var entry> 
mv /varcopy /var

I think the message on boot.log concerning the fact the system can not unmount /var is linked with the fact /var is a btrfs sub volume.

On each ext4 or btrfs system where /var IS NOT a BTRFS sub volume I have no error concerning the unmount procedure.
I have verified again this morning on my three other computers (two in ext4 and one in btrfs) /var is not in fstab even if the root folder (/) is btrfs.

2

No, that’s a bad idea.

If “/var” is not a subvolume, then there will be multiple versions of “/var” saved in snapshots. And since “/var” changes often, expect your root file system to fill up quickly.

I don’t lime that “not unmounted” message, but I don’t think it causes actual problems. I’m pretty sure that there’s an open bug report on it.

I think the message on boot.log concerning the fact the system can not unmount /var is linked with the fact /var is a btrfs sub volume.

Yes, it is. I mainly use “ext4” and I don’t run into that problem (except when I experiment with “btrfs”).

3

I didn’t expermiented to reassure you ^^

And as there is only one error message at shutdown/reboot on the logs… this is not very important.
Thank you take care of you and your beloved ones ^^

4

No, it is not. It does not matter that /var is subvolume - what matters is that /var is separate mounted filesystem. You would see the same issue if /var were ext4 on separate partition.

5

That’s probably true. But very few openSUSE users are doing that.

6

I’m getting also the error of not unmountig on reboot/shutdown, but that is because I have a persistant journal.
Also on btrfs subvolume.