I'm aware of the this question and these are similar issues:
But I couldn't figure it out entirely.
What I did before the error:
I accessed the tmp
folder with Nautilus (sudo
rights) and changed the permissions so that possibly every process is allowed to write here (that was probably very stupid).
Error analysis:
As some posts suggest in the thread I did df -h
:
/dev/sda6 size: 7.4G Used: 7.1G Avail: 0 Use%: 100% Mounted on /
However, running rm ~/.xsession-errors
and
mkdir ~/.xsession-errors
(as suggested) did not do anything (multiple reboots inbetween). How can I check which file is so big to flood /dev/sda6
(I have a hard time to cd
there) and how may I get rid of it?
I'm not an advanced user so please bear with me if I used wrong vocabulary or cannot see an obvious solution.
sudo du -kxa / | sort -nr | head
gives mesort: write failed: /tmp/sort[6 random letters, e.g. SFyDay]: No space left on device.
So thetmp
folder is full right? Is there a way to reset it? Can it cause more harm to mess with this folder or is it usually resettet anyway with system boot? – Stockfisch Feb 08 '13 at 21:51