I suggested that you run
sudo btrfs subvolume list / so you could see all on the system. You limited that output to only the subvolumes at /run/media/liveuser/fedora_localhost-live which is not the entire system by any means.
However, I can see that /dev/sda is btrfs (currently unmounted and data not shown_
/dev/sdb1 is efi
/dev/sdb2 is ext4 (probably /boot)
/dev/sdb3 is btrfs, probably the the main OS volume, but the way it was mounted is not accessible.
The subvolume command shows that you have 438 subvolumes on /dev/sda3, almost all are at
root/var/lib/docker/btrfs/subvolumes/ so you have ~435 docker subvolumes and from fdisk we can see that /dev/sda3 is 97% full of those docker subvolumes.
For recovery you will need to mount the main file system as follows in prep for a chroot into the installed OS.
- Again boot to the live media
- use the
su command to gain root access
- Unmount all you have mounted at /run/media/liveuser/
mount -t btrfs -o subvol=root,compress=zstd:1 UUID=f3f27a6b-6113-48d0-9e4e-26cf67f89b77 /mnt
for i in "/proc" "/sys" "/run" "/dev" ; do mount -o bind "$i" /mnt"$i" ; done
now run the mount command to verify that everything is mounted properly.
mount and look at the mount points /, /home, /boot, /boot/efi, /dev, /run, /proc, /sys. All should be listed and all should be as just done.
At this point you should be in the main installed OS as root and can do the recovery from having docker completely fill the root subvolume with docker subvolumes.
I do not work with docker so cannot help with that, but I am 100% certain that the reason you cannot log in regularly is the fact that the main OS has no free space in the file system and this gets you to a point where you can begin to clean it up.
I have no idea who may have been following this thread to this point, but there may be someone who is experienced with docker that can assist with a proper clean up of the runaway docker config and cleaning out all its subvolumes.
If you get no additional response in the next day then please open a new thread for assistance in cleaning up the docker processes and removing the hundreds of docker subvolumes. Be sure to reference this thread if a new one is started.
There is one thing that may recover some space for you.
dnf clean all to clean out all the normal dnf cache data.
dnf system-upgrade clean to clean out the cache data from the system upgrade.
I do not know how much room will be freed up, but if the output of
df shows that / and /home have dropped below 90% then it is likely that you could reboot and log in normally (depending upon where in the upgrade it may have halted)
I just ran
dnf clean all and freed up almost 20 GB of space from cached cruft of long term updates without manually cleaning it out.
Just as an FYI, whenever in a chroot environment the way to get back to the live media environment is the