Zero Free Space Problems
After recently compiling a kernel for a friend I found an interesting issue. Partition selection had not been the best during installation and there was 10G on the root partition. With the installation of this new kernel we had literally 0 free space on the hard drive. When trying to boot I got this error: “gconf-sanity-check-2 exited with status 256” Possibly the first time that I have ever had a cryptic issue with linux. Google searches just turned up file permission issues but the permissions were right. I then deleted the .gconf and .gconf2 folders in the home folder with no change. In the end I moved / to a different partition with some free space and Viola the problem was fixed.
So I was always under the impression that Linux could run with Zero free space and be just fine because swap space has a dedicated partition. Apparently I am wrong. I assume that gconf needs to write things to /tmp and with no free space I can’t. Anyone have any other specific experience with no free space?
Tags: Random