How can I access the full storage on Fedora 36

Hi ! So I recently installed Fedora workstation (I’ve been using debian) and I’ve just noticed that my full storage shows like 17go with df -H, the root of the filesystem is /dev/mapper/fedora_fedora-root, but i know for sure that I have a lot more, I can even see it with fdisk and gparted, so how can I access my real memory how can I set the root of the filesystem to be “/” and disable /dev/mapper thing I think it is because the /home/ partition is separated (I’ve never done that before and for the install it was auto)

1 Like

Hey,

Could you provide first block device listings you mentioned? Interesting information:

  • df -h
  • lsblk
  • mount | grep mapper

After that we can probably guess disk layout and structure of partitions and mounts and can give you suggestions accordingly or ask further questions :slight_smile:

1 Like

With an auto install of fedora 36 you likely now have the following disk layout by default (which should be confirmed with the outputs requested above).
~300 MB vfat as ESP and mounted at /boot/efi
~1 GB ext4 and mounted at /boot
remainder as btrfs containing subvolumes mounted at / and /home.

The btrfs subvolumes are probably initially limited in size but can grow dynamically to the size of the btrfs partition.

df or df -h should show both / and /home with matching UUIDs and identical sizes and used percentages.

Please also add to the above requested outputs the result of cat /etc/fstab and be sure to post all requested output within the </> Preformatted text tags available on the upper toolbar when you are creating the post.

Thank you guys, I wasn’t home until now that’s why I respond now, and I wasn’t allowed to uplaod multiple images that’s why it’s all on the same
I’ll let you see the commands :

That is difficult to read. Please post the same as text copy/pasted from the screen into the text you post here.

If I am reading that correctly it seems you did not do an automatic install.
You have / on an xfs file system in a 15GB partition and do not have btrfs. An automatic install would have created the btrfs partition and file system for the entire size of the drive as noted above.

You also did not create a separate partition with file system for /home so the allowed 15GB contains both the OS and the files in your home directory.

I do not and never have used xfs so cannot say exactly how to expand it, but it is likely that it can be done with gparted and expand the partition the same as any other partition.

This is a guess, but it seems xfs requires the use of the mapper syntax so you probably cannot, and would not wish to try to, delete that form of access.

Yet I did an auto install, I even re-install it two days ago because at first I thought I had this storage left because of an update (after an update I was forced to create a new user and couldn’t use my old account afterward) but after the re-install it was the same thing

[krysoar@KarlPC ~]$ lsblk 
NAME                   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
zram0                  252:0    0     8G  0 disk [SWAP]
nvme0n1                259:0    0 476,9G  0 disk 
├─nvme0n1p1            259:1    0   600M  0 part /boot/efi
├─nvme0n1p2            259:2    0     1G  0 part /boot
└─nvme0n1p3            259:3    0 475,4G  0 part 
  └─fedora_fedora-root 253:0    0    15G  0 lvm  /

[krysoar@KarlPC ~]$ mount | grep mapper
/dev/mapper/fedora_fedora-root on / type xfs (rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota)
[krysoar@KarlPC ~]$ df -h
Sys. de fichiers               Taille Utilisé Dispo Uti% Monté sur
devtmpfs                         4,0M       0  4,0M   0% /dev
tmpfs                            7,7G    3,6M  7,7G   1% /dev/shm
tmpfs                            3,1G    2,3M  3,1G   1% /run
/dev/mapper/fedora_fedora-root    15G     14G  1,7G  90% /
/dev/nvme0n1p2                  1014M    207M  808M  21% /boot
/dev/nvme0n1p1                   599M    6,2M  593M   2% /boot/efi
tmpfs                            7,7G     40K  7,7G   1% /tmp
tmpfs                            1,6G    128K  1,6G   1% /run/user/1000

cat /etc/fstab
/dev/mapper/fedora_fedora-root /                       xfs     defaults        0 0
UUID=7bef2c5a-d3c4-4643-bdff-06e2bc4c0897 /boot                   xfs     defaults        0 0
UUID=B1E3-5F0E          /boot/efi               vfat    umask=0077,shortname=winnt 0 2

You have the small partitions for /boot and /boot/efi, that’s correct. p3 is assigned as physical volume for the "logical volume manager lvm, which reserved 15G for fedora_fedora-root, which is rather small. The rest of the physical volume should be assigned to a home logical volume, but I do not see it. I do not know whether you can use, from a live system, “gparted” to increase the size of the root partition and add a home logical volume, but you can give it a try.

Thank you I may try that, otherwise do you know from the fedora installer how can I choose that the system use almost the whole disk ?

@h.janssen gave the proper diagnosis here.

What you could do here is basically resize physical volume and then logical volume on top of it.

Per lsblk output I can see that the partition is already the correct size. What probably happened during the installation process is that you removed /home logical volume/mount and LVM for / hasn’t reclaimed all of the space. To do that, you should have edited the size of that volume within the installer. Removing any number and clicking apply would basically use “whatever is available” which would be the full partition.

Anyhow, now you can list the physical volumes:

pvs

from that info you get the exact physical volume. In your case, this is probably /dev/nvme0n1p3 so command for resizing that volume would be

pvresize  /dev/nvme0n1p3

After which you want to extend logical volume (look at lvs):

lvextend -l +100%FREE /dev/mapper/fedora_fedora-root

And as a final step, resize the filesystem on top of the LVM:

xfs_growfs /

Hopefully this helps.

1 Like

Thank you so much it works ! I was so worried about the storage because it was full in some hours of android studio with the gradle cache taking so much, I thought I had to reinstall again you helped me a lot thank you