Req Argh... recovering from disk out of space
#1
For some silly reasons, the disk on my Linux machine ran out of space.

After I cleared that problem, I found that Kodi no longer boots.

Some investigation revealed that /home/kodi/.kodi/userdata/guisettings.xml and /home/kodi/.kodi/userdata/profiles.xml both got clobbered. Zero length.

I set Kodi to create a new .kodi directory, and copied over the new versions. But now I need to reset all my settings.

There were also a jillion log files in /home/kodi that were generated because the profiles.xml file got clobbered. There were too many to delete via "rm *.log" (too many arguments), so I had to figure out a shell command for that.

Also, my web remote control stopped working, since the web interface defaults to "false".

I am wondering how this mess happened, and my only guess is that Kodi tried to rewrite these XML files when no disc space was available, and they both ended up clobbered.

To be precise, I didn't change these setttings files, but nevertheless Kodi tried to re-write them.

Feature request...

Would it be possible to have Kodi check that disc space is actually available, before re-writing these files?

If that were done, Kodi would be (IMHO) more robust, and it would be a lot easier to recover from this sort of problem.

Edit: I'm using the latest latest build of Kodi.
Reply
#2
(2019-08-14, 04:14)mrob Wrote: Would it be possible to have Kodi check that disc space is actually available, before re-writing these files?
If that were done, Kodi would be (IMHO) more robust, and it would be a lot easier to recover from this sort of problem.
It's probably not impossible to implement it, but it would be another instance that gets Kodi bloated and has to protect itself from what I would call "outside interference". A drive running out of space? IMO, Linux guys are usually the more technical and observant people. You already know why you ran out of disk space?

Also, keeping a backup copy of Kodi's profile isn't too difficult. And, "latest" is not an acceptable version number. Wink

(2019-08-14, 04:14)mrob Wrote: There were also a jillion log files in /home/kodi that were generated because the profiles.xml file got clobbered. There were too many to delete via "rm *.log" (too many arguments), so I had to figure out a shell command for that.
Usually crash logs get written only once per Kodi session, so the number of log files is a bit odd.
Got a Kodi problem? Provide us with a full Debug log (wiki) || Usefull pages: First time user (wiki) || Troubleshooting (wiki) || Free content (wiki) || Forum rules (wiki) || VPN policy (wiki)
Reply
#3
Yes, I identified and fixed the cause of the exhausted disk space. I won't bother y'all with the details. Big Grin

It did also occur to me that making a copy of the profile would be a good idea. I'll investigate the guidance here: Backup (wiki)

If there are better ways to do the backup, I'm all ears.

Thanx
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Argh... recovering from disk out of space00