KDE: /home allways full.

ch64 · Guru Joined: 09 Jun 2010 Posts: 412

Hello. I have 20GB for /home.
So my df -m looks like this:

/dev/sdb5 20901 19765 73 100% /home

The problem i have since years is, that my /home is full in a few hours after starting KDE.

I'm often copying big files from /home to another partition. But /home is allways being full.
I can delete 4GB and it takes no 24hours and my /home is full, again.

I have disabled and enabled that AKONADI file indexing in the KDE System settings. But it must be another option.
Somebody can help me to find the thingy, which is making my harddisk full?

I think it's no real content, only tmp files or something.

Thanks, ch64.

eccerr0r · Posted: Mon Jul 14, 2014 2:25 pm Post subject:

See if you have any logfiles that are being written. What are the big files that you have?

Do you have an ~/.Xsession-errors file that constantly is getting larger? You should take a look at that and see if you can fix the problem it's hinting at, then delete that file.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

franzf · Advocate Joined: 29 Mar 2005 Posts: 4565

A nice graphical way to find which files pollute your /home is kde-base/filelight.

ch64 · Guru Joined: 09 Jun 2010 Posts: 412

Filelight is a nice program!
i have much in
file:///home/flash/.kde4/share/apps/nepomuk/ (11.2GB)

I disabled nepomuk in Kmenu/Systemsettings now. Can i delete the files in it? Yes?

Another thing is:
-rw-r--r-- 1 flash users 9,1G 14. Jul 15:18 soprano-virtuoso.log

It's in that directory: /home/flash/.kde4/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log

The log is full with that content:

franzf · Advocate Joined: 29 Mar 2005 Posts: 4565

Disabling (systemsettings or USE="-semantic-desktop") + deleting should be save. Alternatively, if you like indexing files, you can switch to >=kde-4.13, which replaces the whole crappy virtuoso (well, not entirely crappy, but too feature-rich for a simple task like nepomuk) +soprano + nepomuk with an own implementation - baloo - which seems to have quite a good performance.

eccerr0r · Posted: Mon Jul 14, 2014 7:04 pm Post subject:

Usually if you don't get the file space back after deleting a file, it's because there's still something accessing the file. Try killing/restarting <nepomuk> or better yet logout and login and the kernel should then release its space.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

NeddySeagoon · Posted: Mon Jul 14, 2014 7:06 pm Post subject:

ch64,

When you delete an open file, *nix removes it from the directory, so it no longer appears in ls.
However, the content is not actually removed and the space freed, until the file is no longer in use.

You can use lsof to see what program(s) have the file open.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

lyallp · Posted: Wed Aug 06, 2014 10:32 am Post subject:

Nifty, I just tried filelight.

Not bad. Found about 5GB of ~/.thumbnails I did not realise I had!

Says something about storage nowadays when I 'discover' 5GB.

I am not old, honest!
_________________
...Lyall