On Mon, Apr 02, 2012 at 11:55:02AM -0600, Paul E Condon wrote: > During my tests, I noticed that there was always a line in df, > concerning /tmp in tmpfs. With RAMTMP=yes the line was labeled tmpfs, > but with RAMTMP=no, the line was labeled 'overflow', or something else > that I misremember as overflow. Now I surmise that tmpfs is being used > during boot whatever the setting of RAMTMP, and is not being shut down > correctly towards the end of the boot process after the loader is > capable of reading /etc/defaults/rcS. Of course, it can't be as > simple as that, and of course, I can't really understand, but that's > the best I can come up with. There are reasons why I am not a DD.
Have a look at /etc/init.d/mountoverflowtmp. Your root filesystem is full. This triggers the mounting of a tmpfs on /tmp *irrespective* of the RAMTMP option, in order to allow you to log in. Solution: free up some space on your root filesystem, and all will return to normal. Mounting a filesystem on /tmp would have solved this specific problem by making more than a megabyte of free space available, which would avoid triggering this condition. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120402205619.gq30...@codelibre.net