The system is x86_64 and I'm using brtfs. So that clears that up:
findmnt --notruncate /
TARGET SOURCE FSTYPE OPTIONS / /dev/nvme0n1p10[/root00] btrfs rw,relatime,seclabel,ssd,space_cache,subvolid=276,subvol=/root00
findmnt --notruncate /home
TARGET SOURCE FSTYPE OPTIONS /home /dev/nvme0n1p10[/home] btrfs rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/home
However, it's still confusing to me having df show that both /home and / are filled up when du -s shows that /home is only using 96G. I found the problem by doing du -s /usr/* and saw that /usr/local was consuming a lot of space.
du -s /home 96971060 /home
du -s / 5436965761 /
Paolo
On 2/6/22 08:49, Francis.Montagnac@inria.fr wrote:
Hi.
On Sun, 06 Feb 2022 11:42:22 -0500 "Garry T. Williams" wrote:
You probably have / and /home on subvolumes of a btrfs file system.
+1
The clearer way to see that is probably to use:
findmnt --notruncate / findmnt --notruncate /home
Example: see the subvol= option:
findmnt --notruncate / TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/luks-c92191d5-7811-49f9-867c-1e300d1e9410[/root] btrfs rw,relatime,compress=lzo,ssd,space_cache,subvolid=258,subvol=/root
findmnt --notruncate /home TARGET SOURCE FSTYPE OPTIONS /home /dev/mapper/luks-c92191d5-7811-49f9-867c-1e300d1e9410[/home] btrfs rw,relatime,compress=lzo,ssd,space_cache,subvolid=257,subvol=/home
That is the current default configuration now.
But it was not in F31 ...