recently installed SSD gets full {solved}

[jpg153]

Hi all,

today I found out that the SSD I recently installed is already occupied to 97% - which is at least not possible from my usual activities.
Its a 256GB drive and before I installed this SSD I was using a 60GB SSD which still had some spare memory (and still use it).

How to find out what/who consumes so much diskspace?

Thanks.

[DidierSpaier]

You don't say what you store on your SSD. Let's assume it is mounted as /ssd. Type:

Code: Select all

du -h --max-depth=1  /ssd

and provide the output. .

Please also provide the output of following commands:

Code: Select all

cat /etc/fstab/
lsblk -o model,name,size,fstype,mountpoint
df -h|grep ^/dev

[jpg153]

Hi Didier,

its my "home"...

Code: Select all

jpg[~]$ du -h --max-depth=1 /home
33G	/home/backup
0	/home/.Trash-1000
1,9M	/home/ftp
du: das Verzeichnis '/home/jpg/.cache/webkit' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jpg/.cache/xfce4' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jpg/.cache/xine-lib' kann nicht gelesen werden: Keine Berechtigung
192G	/home/jpg
du: das Verzeichnis '/home/jupaga/.config/Thunar' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.config/pulse' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.config/xfce4/desktop' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.config/xfce4/xfwm4' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.dbus' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.gnupg' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis '/home/jupaga/.gvfs' kann nicht gelesen werden: Keine Berechtigung
1,1M	/home/jupaga
5,7M	/home/smbgast
225G	/home
jpg[~]$ 

Code: Select all

jpg[~]$ cat /etc/fstab
PARTUUID="22e7fbee-01"        /                xfs         defaults,relatime,discard         1   1
PARTUUID="759dcbc5-05"        /home            xfs         defaults,relatime,discard         1   2
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro,comment=x-gvfs-show 0   0
#/dev/fd0         /mnt/floppy      auto        noauto,users,rw,umask=00 0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0
tmpfs			/tmp  			tmpfs 	defaults,noatime,mode=1777	0 0
tmpfs			/var/tmp		tmpfs	defaults,noatime,mode=1777	0 0
#PARTUUID="16de707e-05"		/home2			xfs         defaults,relatime         1   2
#PARTUUID="16de707e-01"		/5gbstore		ext2         defaults,noatime         1   2
PARTUUID="22e7fbee-02"		/salix32		ext2         defaults,noatime         1   2
PARTUUID="22e7fbee-05"		/reserve		xfs         defaults,relatime         1   2
jpg[~]$ 

Code: Select all

jpg[~]$ lsblk -o model,name,size,fstype,mountpoint
MODEL            NAME     SIZE FSTYPE MOUNTPOINT
OCZ-VERTEX2      sda     55,9G        
                 ├─sda1  18,8G xfs    /
                 ├─sda2  10,8G ext2   /salix32
                 ├─sda3     1K        
                 └─sda5  26,4G xfs    /reserve
Samsung SSD 750  sdb    232,9G        
                 ├─sdb1     1K        
                 └─sdb5 232,9G xfs    /home
DVD-ROM SH-D163B sr0     1024M        
DVDRAM GH22NS70  sr1     1024M   

Code: Select all

jpg[~]$ df -h|grep ^/dev
/dev/root        19G    8,3G   11G   44% /
/dev/sdb5       233G    226G  6,9G   98% /home
/dev/sda2        11G    2,8G  7,3G   28% /salix32
/dev/sda5        27G     33M   27G    1% /reserve
jpg[~]$ 

I doubt that I have files amounting to 225GB...at least I could not identify files/directories of that size or which in sum would make it that big..

Thanks.

[DidierSpaier]

I doubt that I have files amounting to 225GB...at least I could not identify files/directories of that size or which in sum would make it that big..

Really?

Code: Select all

jpg[~]$ du -h --max-depth=1 /home
✀-----
33G	 /home/backup
✀-----
192G /home/jpg
✀-----
225G  /home

It seems me that 33+192 is pretty close to 225, isn't it?

I'd look into /home/jpg...

[jpg153]

Hi Didier,

certainly I will!

But, how to find out if there are hidden or maybe corrupted files which are either that big or do report or wrong size?
From what I have seen so far I could not find files/directories which are that big - but I will for sure have another look
and a more exact calculation on that.

What concerns me is simply, I had the 60GB SSD and a 70GB HDD before and the 70GB was replaced with the 256GB SSD.
So even if I now have Virtual box installed with some images and some videos filed (I know them!) on that drive, I still
doubt it would be more than 100GB...

I will give you more details later this evening.

Thanks.

[DidierSpaier]

To investigate:

Code: Select all

du /somedir -h --max-depth=1 # to find big directories, including the hidden ones
ls -lha /somedir # to find big individual files, including the hidden ones
# then if /somedir/somesubdir is big:
du /somedir/somesubdir -h --max-depth=1
ls -lha /somedir/somesubdir
# and so on.

You can filter the big files using grep.

Use the du command as root to avoid most of the "kann nicht gelesen werden: Keine Berechtigung" messages.

You can also use the find command. For instance:

Code: Select all

find /home/jpg -size +500M

"man find" will tell you more.

[jpg153]

Hi Didier,

well with

Code: Select all

du -h --max-depth=1

I found (as expected) the reason...

Code: Select all

jpg[~]$ du -h --max-depth=1
45M	./.adobe
du: das Verzeichnis './.cache/webkit' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis './.cache/xfce4' kann nicht gelesen werden: Keine Berechtigung
du: das Verzeichnis './.cache/xine-lib' kann nicht gelesen werden: Keine Berechtigung
146G	./.cache

Which means ".cache" eats up my disk space.
It contains almost 3 million objects in "thumbnails".

Now
1. where do they come from?
2. how to clean them up?
3. how to avoid getting in the same situation again?

or, is that normal?

Thanks.

[DidierSpaier]

You need to look closer, including running "du -h --max-depth=1 /home/jpg/.cache" and so on.

1. These files come from something you have installed or downloaded. Check their dates to see since when they are there, and if that matches the date when you installed or downloaded something that could be related.

2. You are supposed to know how to remove files, aren't you?

3. It depends on the answer to question 1.

[jpg153]

Hi Didier,

indeed, its something I installed which does eat up diskspace - its Thunar!

Everytime I open a folder containing images (from camera via USB or from filed images on disk) Thunar creates the preview images which are stored in

Code: Select all

.cache/thumbnails/normal/

My standard setting in Thunar is the "symbol view".

Maybe I need to change that or use a different file manager, as previewing photos is a must have.

I will mark this solved later on...

But, any other way to prevent the disk is getting filled up again?

Thanks.

[ChuangTzu]

That would be strange behavior for thunar, what is the size of your images/photos?

Curious, because i've never encountered a problem like that.

If needed, but not sure if it would make a difference, these are good alternative FM's with a GUI:
pcmanfm
spacefm
xfe