Lost space on root partition

OK, I was dumb. I have two drives hhd and ssd. The ssd was to full so I moved home to the HHD but messed it up. After recovering from my problems I found that the root SSD drive still has 12 gb (size of home) missing. How do I get it back.

Filesystem Size Used Avail Use% Mounted on
DF -ha /dev/sdb2 93G 87G 1,6G 99% /

Filesystem Inodes IUsed IFree IUse% Mounted on
DF -iha /dev/sdb2 6,0M 1,7M 4,4M 28% /

lsblk /dev/sdb2 -o size
SIZE
94,4G

Happy to post any other info needed. :smiling_face:

It depends on what you did.
Did you use command line to move your $HOME directory (or it’s contents) around?
if so - it’s easy to re-trace your steps by using the shell history.

You better explain exactly what you did and how you did it
in order for others to understand the issue.

How do you know that?

Where is your $HOME now?
Back on the SSD?
Do you still have the copy from where you moved it to the HDD?

ls -hl /
ls -hl /home
ls -hl /home/username

I’m not sure I understand you correctly, but if you are saying that you had expected your root filesystem to have regained 12 GiB of free space after moving the contents of /home to the other drive, then you most likely didn’t move those contents, but you rather copied them.

In that case, you need to empty the directory /home on the root filesystem, but given that /home is now a mountpoint for the volume on the other drive, the contents of that directory are now hidden by the contents of the other volume. Therefore, you’re going to have to bind-mount the root filesystem in order to clean that out. :arrow_down:

sudo mount -o bind / /mnt
sudo rm -rf /mnt/home/*
sudo umount /mnt

I think you understand the problem. I don’t really get how your answer works. Clearly you are mounting the lost /home and rm it but why does this mount get the old file tree and not the new one?

Also get an error when I try it.
rm: cannot remove ‘/mnt/home’: Device or resource busy
I must go to a different user lever or something?

Thanks!!!

Because the normal/active system runs with a partition mounted at /home, but by bind-mounting the root directory ─ note: “directory”, not “filesystem” ─ to /mnt, you are making the contents of the root filesystem itself available at a second location, namely under /mnt, without that the filesystem mounted at /home is included in that bind-mount.

As such, the directory /mnt/home will show you what is in the directory /home when the filesystem for /home isn’t mounted.

It was a typo in my previous post, which I have now corrected. It should be /mnt/home/*. :wink:

OK, none of that worked as it should but still after rebooting DF is reporting as it should.
/dev/sdb2 93G 76G 13G 87% /
But Filelight is saying that / root is 85.1 Gib and 100% full. ???
I am confused still. LOL.
Next step?
Thanks again!

What is the output of… :arrow_down:

df -Th 2>/dev/null

df -Th 2>/dev/null  :heavy_check_mark:

Filesystem     Type      Size  Used Avail Use% Mounted on
dev            devtmpfs  7,8G     0  7,8G   0% /dev
run            tmpfs     7,8G  1,7M  7,8G   1% /run
/dev/sdb2      ext4       93G   76G   13G  87% /
tmpfs          tmpfs     7,8G   57M  7,8G   1% /dev/shm
/dev/loop0     squashfs  128K  128K     0 100% /var/lib/snapd/snap/bare/5
/dev/loop2     squashfs   56M   56M     0 100% /var/lib/snapd/snap/core18/2253
/dev/loop3     squashfs   85M   85M     0 100% /var/lib/snapd/snap/plexmediaserver/252
/dev/loop4     squashfs   44M   44M     0 100% /var/lib/snapd/snap/snapd/14295
/dev/loop1     squashfs  100M  100M     0 100% /var/lib/snapd/snap/core/11993
/dev/loop5     squashfs   56M   56M     0 100% /var/lib/snapd/snap/core18/2284
/dev/loop6     squashfs   85M   85M     0 100% /var/lib/snapd/snap/plexmediaserver/257
/dev/loop8     squashfs   44M   44M     0 100% /var/lib/snapd/snap/snapd/14549
/dev/loop7     squashfs  111M  111M     0 100% /var/lib/snapd/snap/core/12603
tmpfs          tmpfs     7,8G   56M  7,8G   1% /tmp
/dev/sdc1      ext4      917G  833G   39G  96% /mnt/OneT
/dev/sdb1      vfat      300M  288K  300M   1% /boot/efi
/dev/sda1      ext4      2,7T  1,8T  815G  69% /mnt/ThreeT
/dev/sda2      ext4       20G   13G  5,6G  70% /home
tmpfs          tmpfs     1,6G   92K  1,6G   1% /run/user/1000

Your root filesystem appears to have 13% of free space left. It is however possible that FileLight gives you the wrong output because of the Snaps. I believe I’ve heard of that before.

It is mounted on /dev/sda2

What flag?

UUID=5B30-D590 /boot/efi vfat umask=0077 0 2
UUID=dbd31db8-c554-4004-a993-cb875db9a9b4 / ext4 noatime 0 1
UUID=5dff71de-73ea-42a4-b872-246fc202ca51 swap swap noatime 0 0

UUID=52e2f09a-560e-4d0a-97db-cca80831542b /mnt/OneT ext4 relatime,discard 0 2
UUID=d7d418ac-04c8-438d-8bbb-fae812d032ff /mnt/ThreeT ext4 relatime,discard 0 2

UUID=d4af13c3-8a3f-4e08-a35d-5beac27abb8c /home ext4 auto,nouser,defaults,nodev,relatime 0 0