kde4 profile got corrupted due to insufficient disk space?

hi.
yesterday i’ve ran out of disk space in my /home (in whole the single / partition in fact :smiley: ). when i noticed this i managed to free about 1,5 gigs in it. kde4 session went on without a hitch.
but today i rebooted my laptop and guess what? after logging in in kdm i just saw default suse wallpaper instead my custom one, no taskbar, no plasmoids, not a speck on desktop. according to `ps -fu $USER’ some of kde4 processes were running though.
and all this mess because of short disk space shortage? what a shame!

PS. a, yeah. the question! the question is - how to fix this issue? i already recreated whole .kde4 two times and wouldn’t do it for third.

> how to fix this issue?

neither Unix nor Linux likes to run out of disk space…been that way
forever…and, it has always been the system administrators ‘job’ to
not let that happen…

perhaps with more and more ‘users’ trying to self-administer Linux
someone has built a program (or three) which constantly monitors all
available drives and then alerts you to impending danger

i guess you might find an open source “disk space monitor” program to
do that at sourceforge.net

but, until you install one to “fix this issue” as you ask, the answer
is simple: avoid the problem by not running out of space.

to repair the damage caused, i wouldn’t know how to complete the task
but i do know the first few steps are:

  1. Provide more disk space (expand or offload unneeded/old data and
    programs)

  2. Routinely monitor available disk space

  3. Establish and stick to a maximum percentage of disk usage prior to
    beginning again at step one. [personally i use 80% full as the spot
    where i begin either buying new hardware or dumping/saving off old
    data and increase step two’s monitoring to daily, at least…]

  4. then, you might try inserting the DVD and try the “Repair Installed
    System” option at
    http://en.opensuse.org/INSTALL_Local#Installation

and/or
http://en.opensuse.org/INSTALL_Local#Step_3:_Installation_Mode

NOTE: i do not know if the DVD repair function is even close to being
able to solve all the problems which might occur if the systems’
drive is filled…


goldie
Give a hacker a fish and you feed him for a day.
Teach man and you feed him for a lifetime.

Note: Accuracy, completeness, legality, or usefulness of this posting
may be illusive.

A live CD booted and started as root will let you delete files to free up space. But obviously you need to be careful. You need to shift-delete or enable delete in the context menu.

Restore from your latest backup (shouldn’t be older then say about a week).

Jesus. what’re you people talking about? 80% free space, rescue CD. i began to think my post was slightly misleading. and that i’m in need for XP disk array to be installed in my apprtment :slight_smile:

the system runs fine. except user profile became broken. i don’t need to repair system.

so, to summarise, you guys don’t know. you should just say that. that’s it.

2goldie: all unixes (including linus) are very tolerant to disk space shortages.

But you need a backup. And when you do not have it, you need to think about a backup strategy, including backup media, tool, what, how often, etc.

@-error

so, to summarise, you guys don’t know. you should just say that. that’s it.

Sounds like you have it all in hand.
We’re real dummies!

please note, you said it yourself :slight_smile:

> the system runs fine. except user profile became broken.

define what you mean by “user profile” and maybe someone can help…

> 2goldie: all unixes (including linus) are very tolerant to disk space
> shortages.

you are obviously more knowledgeable on that subject than i am…

probably because you have witnessed filling a disk, with no ill
effects whatsoever…

right?


goldie

i belive, that some file in ~/.kde4 became corrupted.

> 2goldie: all unixes (including linus) are very tolerant to disk space
> shortages.

you are obviously more knowledgeable on that subject than i am…

probably because you have witnessed filling a disk, with no ill
effects whatsoever…

right?

i strongly believe that problem is in the way which kde saves its configuration files. and it has nothing to do with *nix. i think it just began overwriting files when error occurred. imho, not way to go. better way is to write to temp file and if everything went alright rename it. but things are as they are.

> i belive, that some file in ~/.kde4 became corrupted.

then you might try:

  • backup /home/[you]/.kde4
  • add a new user
  • compare all files in /home/[you]/.kde4 to their counterparts in
    /home/[new user]/.kde4
  • overwrite /home/[you]/ files with /home/[new user]/ one at a time
    until you like what you see…
  • when you like what you see then go back and replace all but the last
    overwritten file with /home/[you]/.kde4/[backup]

> i strongly believe that problem is in the way which kde saves its
> configuration files. and it has nothing to do with *nix.

i strong believe the Linux kernel does NOT behave well (fail
gracefully) when a disk is full and it can not write to disk (say, a
kde config file, or any file)…how KDE reacts, i don’t know…it
makes no difference if the kernel has already gone fishing…

ymmv, we need not discuss it further…for me, i’ll make sure it
doesn’t happen here, you do as you wish.


platinum