Disk use analyzer claims almost out of space

[kpatz]

It's more readable if you put [code] before and [/code] after the output when you post it here.

Like this:

[code]jess@ranha-system:~$ df -hT|egrep '(^/(dev|[:/])/|zfs)' | grep -v '/dev/loop'
/dev/sda9 ext4 73G 69G 332M 100% /
/dev/sda8 ext4 104G 47G 52G 48% /media/jess/a2aad275-090f-490e-a903-e4b68f52eb19
/dev/sda6 ext4 178G 100G 69G 60% /media/jess/77aacfae-f704-422a-82f5-047bb0dcb95f1
/dev/sda1 ext4 86G 14G 68G 18% /media/jess/d936da7d-f118-4a64-87cb-ea8377a17d59
/dev/sdb1 ext3 976M 60K 976M 1% /media/jess/897fbe47-71a3-4afa-9722-109fc80bc2a4
/dev/sdb3 ext3 431G 75G 356G 18% /media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a
/dev/sdb2 ext3 500G 78G 423G 16% /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3
jess@ranha-system:~$ [/code]

The result in your post will look like:

jess@ranha-system:~$ df -hT|egrep '(^/(dev|[:/])/|zfs)' | grep -v '/dev/loop'
/dev/sda9 ext4 73G 69G 332M 100% /
/dev/sda8 ext4 104G 47G 52G 48% /media/jess/a2aad275-090f-490e-a903-e4b68f52eb19
/dev/sda6 ext4 178G 100G 69G 60% /media/jess/77aacfae-f704-422a-82f5-047bb0dcb95f1
/dev/sda1 ext4 86G 14G 68G 18% /media/jess/d936da7d-f118-4a64-87cb-ea8377a17d59
/dev/sdb1 ext3 976M 60K 976M 1% /media/jess/897fbe47-71a3-4afa-9722-109fc80bc2a4
/dev/sdb3 ext3 431G 75G 356G 18% /media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a
/dev/sdb2 ext3 500G 78G 423G 16% /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3
jess@ranha-system:~$

It uses a monospace font so the columns line up better, and it separates out from the rest of the post to make it more readable. An easy way: type [code] into the reply box, then paste (Ctrl-V) your output, then type [/code].

That said, your root filesystem (/dev/sda9) is still 100% full. Get those deja dup files out of your home. Put them on one of those other drives/partitions.

Are any of these devices external (USB) drives?

[Gnusboy]

Kpatz

Yes, these are both external drives.

/dev/sdb3 ext3 431G 75G 356G 18% /media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a on the 462GB
/dev/sdb2 ext3 500G 78G 423G 16% /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3 on the 537 GB

But when I try to move the files onto either of these drives, I keep getting the the same error message saying there is no space left on drive. It happens whether I try to copy and move, move to a different location on either on the main internal drive or on either of the external drives. These are the usual messages, but I noticed that they are not exactly the same.

Error opening file '/media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a/Trash-1000/files/RioRanha/duplicity-full.20181219T220352Z.vol42.difftar.gz': No space left on device (/trash-1000/files)
Error opening file '/media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a/home/jess10.2015 BK/duplicity-full.20181219T220352Z.vol21.difftar.gz': No space left on device (/home/jess10.2015 BK)
Error opening file '/media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a/duplicity-inc.20181221T214143Z.to.20190102T193356Z.vol6.diff tar.gz': No space left on device (/duplicity-inc.20181221T214143Z.)

So I'm stymied. Maybe I'm not using the right way to do it. Isn't it supposed to be ... highlight, copy and drop into another folder no matter which drive.
It also won't allow me to make a new folder or put the items into it.

Now I'm stuck for time and have to leave. I'll have to continue this later. I think I am about to have a catastrophe. So I've gotta figure it out. Thank you for your help, I appreciate it.
I'll check back when I get to it.
Here's a shot with some info too

/home/jess/Pictures/Deja Screenshot 06-11-2019.png
file:///home/jess/Pictures/Screenshot%20disk%20use%20analyzer%20A%202019-06-08.png

[kpatz]

EDIT... removed all the stuff I posted earlier... here's a simpler solution. Do these from the command line... if you use the GUI, you may get space errors. Also, by default deleting files in the GUI just moves them to a trash folder, freeing up no space (Shift-Delete gets around this).

1. Backup your entire home directory to one of your external drives (we'll use the 500GB one):

rsync -avx ~ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup

(You can use something other than homebackup as the folder name... I just provided that as an example).

2. Start nuking stuff wholesale from Home now that it's backed up.

cd ~
rm -r .local/share/Trash
rm *.difftar.gz
rm -r trash-1000 Trash-1000

I'm assuming the *.difftar.gz files are all directly in home and not in a subfolder of home... if they're in a subfolder, nuke them there as well.

Check the free space with df /. If it's less than 100% now, you should be able to delete/move more stuff using the GUI. If it's still 100%, rm -r ~/.cache next, or find more deja dup files to delete. Empty the trash regularly when using the GUI to move/delete files. Close any browsers or other applications you might have running before nuking .cache.

Then run the command du -hd 1 ~ to see if we have any more folders taking up a bunch of space.

[Gnusboy]

Kpatz

When I entered the code you gave me this is the result. It doesn't appear that rsync is creating a new folder to put this stuff in.

jess@ranha-system:~$ rsync -avx ~ /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup
sending incremental file list
rsync: mkdir "/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup" failed: No space left on device (28)
rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1]
jess@ranha-system:~$

As this didn't work, I searched for something else and came up with this:
================================================== ================================================== ================================================== ====
"I had the same issue, the destination directory had enough space but I'd get "No space left on device". Turns out rsync copies the file to somewhere else first, then moves it to the destination directory. To change this behavior, use --inplace.


According to https://download.samba.org/pub/rsync/rsync.html "This option changes how rsync transfers a file when its data needs to be updated: instead of the default method of creating a new copy of the file
and moving it into place when it is complete, rsync instead writes the updated data directly to the destination file."

rsync --inplace source destination

Helpful or not?

[kpatz]

It's saying no space on device when it tries to mkdir on the destination.

First, make sure that destination is mounted (type mount and see if you see /media/jess/d60ed... mounted). If the USB drive isn't attached, it's just going to try and create the directory in the root filesystem which is full. If it's mounted elsewhere, use that as the destination folder instead of /media/jess/d60ed....

If it is mounted, maybe space is needed on / just to run commands like mkdir even on another partition? Try cd-ing to the destination path and making the directory yourself:

cd /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3
mkdir homebackup

If that doesn't work, try it with sudo:

sudo mkdir /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup

This may work because some space in ext4 partitions is reserved for root to use, so the system doesn't crash outright when running out of space. If this works, chown homebackup so your regular user can write to it:

sudo chown jess:jess /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup

Then try sudo moving ONE file or a small group from home to homebackup (I used the asterisk because it looked like there might be a space in the filename):

sudo mv ~/duplicity-inc.20181221T214143Z.* /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup/

If this works, it may free up enough space for the rsync or cp to work to complete your backup. Check with df / before proceeding.

If all else fails you may have to boot a live CD or USB, mount /dev/sda9 and the external, and move the files while the system isn't running with the full filesystem as root.

[garvinrick4]

You can use gparted to create new space if...
Show a screen shot of gparted and we will see. Sometimes quite easy will instruct.
Gparted is a tool to create partitions if you have never used.

[Gnusboy]

I did mount the 537 GB drive and it shows that its open.
This is what I got when I typed mount. It seems like a lot of stuff for a simple command.
I'm not sure what to change to get to the target destination.
Is this correct?

jess@ranha-system:~$ cd /sdb2/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3
jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$ mkdir homebackup
mkdir: cannot create directory ‘homebackup’: No space left on device


jess@ranha-system:~$ cd /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3
jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$ mkdir homebackup
mkdir: cannot create directory ‘homebackup’: No space left on device
jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$
jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1840780k,nr_inodes=460195 ,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode =000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=378816k,mode=755)
/dev/sda9 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_age nt=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,max proto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/var/lib/snapd/snaps/evince_60.snap on /snap/evince/60 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/evince_68.snap on /snap/evince/68 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/chromium_733.snap on /snap/chromium/733 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core18_970.snap on /snap/core18/970 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/gnome-3-28-1804_51.snap on /snap/gnome-3-28-1804/51 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/evince_57.snap on /snap/evince/57 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/vestin_3.snap on /snap/vestin/3 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core18_941.snap on /snap/core18/941 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_6818.snap on /snap/core/6818 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core18_782.snap on /snap/core18/782 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/gtk-common-themes_1122.snap on /snap/gtk-common-themes/1122 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/libreoffice_121.snap on /snap/libreoffice/121 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/firefox_216.snap on /snap/firefox/216 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_6673.snap on /snap/core/6673 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/gtk-common-themes_818.snap on /snap/gtk-common-themes/818 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/gtk-common-themes_1198.snap on /snap/gtk-common-themes/1198 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_6964.snap on /snap/core/6964 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/gnome-3-28-1804_47.snap on /snap/gnome-3-28-1804/47 type squashfs (ro,nodev,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=378816k,mode=700,ui d=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=10 00)
/dev/sdb3 on /media/jess/205504c6-6bf7-4fc0-a732-4ea634c2d00a type ext3 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udi sks2)
/dev/sdb1 on /media/jess/897fbe47-71a3-4afa-9722-109fc80bc2a4 type ext3 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udi sks2)
/var/lib/snapd/snaps/chromium_750.snap on /snap/chromium/750 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/firefox_226.snap on /snap/firefox/226 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/libreoffice_123.snap on /snap/libreoffice/123 type squashfs (ro,nodev,relatime)
/dev/sda8 on /media/jess/a2aad275-090f-490e-a903-e4b68f52eb19 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udi sks2)
/dev/sdb2 on /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3 type ext3 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udi sks2)
jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$

[Gnusboy]

Here's my problem: I don't know how to change the destination to mkdir
Also, the properties on this are root. does this matter\?


d60ed036-350a-4524-833e-c91e7dd76fc3
Folder (inode/directory)
Location:/media/jess
I know I should be able to do this, but ... my brain is totally in the weeds.

[kpatz]

Here's my problem: I don't know how to change the destination to mkdir

You changed your destination when you entered the command:

cd /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3

and your prompt changed to

jess@ranha-system:/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3$

This is telling you your current directory is now /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3.

However, the mkdir still failed. What happens if you sudo mkdir homebackup while you're in /media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3?

Does that work?

Also, are there any large files in your home that you can delete? Ones you don't care about? Maybe deleting works when a mkdir or rsync or cp doesn't.

Also post the output of the command du -hd 1 ~. This will tell you the folders in home and how much space each takes.

[Gnusboy]

This is what I get

[sudo] password for jess:
mkdir: cannot create directory ‘/media/jess/d60ed036-350a-4524-833e-c91e7dd76fc3/homebackup’: No space left on device
jess@ranha-system:/$ sudo mkdir homebackup
sudo: unable to resolve host ranha-system
[sudo] password for jess:
jess@ranha-system:/$ sudo mkdir homebackup
mkdir: cannot create directory ‘homebackup’: File exists
jess@ranha-system:/$