Welcome! If this is your first visit, be sure to check out the FAQ. You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid the CAPTCHA verification when searching . Select Articles, Forum, or Blog. Posting in the Forums implies acceptance of the Terms and Conditions.

Subscription Email:

Currently the Forum email subscription function is not working. The issue has been reported, no E.T.A. for a fix.

Core Network Router Replacement - Provo

OUTAGE PERIOD: 0900 - 1300 MDT 23rd March - There will be a short outage (up to 30 mins) affecting network communications to/from the Provo office. There may be several other short outages on specific services during the change window. This will likely affect access to the openSUSE Forum during this period.

Re: KDE not starting after running Partioner.

It is clear that sda5 is 100% full. And that is your / (root) partition.

/var is only one of the many off springs there.

BTW I assume that sda6 is the /home file system you changed to ext4.

So you have to check what fills up /.

Again that is an heuristic process. You start (as root) at the bottom, in this case /:

Code:

cd /
du -sh *

from what you see there you guess what is out of proportion. Let us assume that is /data (which you probably do not even have), then you go there and repeat

Code:

cd /data
du -sh *

etc. until you think you got the culprit.
It then depends on what you found on how to repair. When it is a log file that runs amok, maybe check what the messages show (because that is what went wrong in the first place) and then emtpty or even remove it (most log files will be recreated when gone).

Re: KDE not starting after running Partioner.

Originally Posted by johngwalker

26G In /tmp !!!!!

Is it going to be safe for me to just delete the lot? Or might there be something there that needs to be saved?

OK, that is something!

As you are now running in run-level 3, IMHO you can delete all there. But first take a look to get an idea of what is still there that probably should have been deleted, or not have being created (stupid idea: a copy of the tar file of /home?).

================================
For making /tmp a tmpfs:
Add an entry into /etc/fstab

Code:

tmpfs /tmp tmpfs size=25%,uid=root,gid=root,mode=1777 0 0

See

Code:

man 8 mount

specialy the section: Mount options for tmpfs.

Before mounting this file system for the first time (either by command, or by reboot) you should clean the present /tmp directory as good as possible. Existing contents will still occupy disk space when you mount a file system over it.

Re: KDE not starting after running Partioner.

Thanks for this advice. I'll have a look at the mans and have a try at setting something up.

/tmp contained a single file of 26G, which was the culprit. This was entirely my fault. After backing up /home I tried to check the tar file using Ark in KDE and it crashed, but everything else seemed to be okay running in command mode so I went on with reformatting the /home partition. So there's no one to blame but myself.