Comment 19 for bug 35217

I experienced the problem of disk space exhausted recently. It worked, i.e. I was able to log in, but nobody warned me so I had to interrupt my work and reboot when I noticed that the tmpfs had been mounted. I don't understand if the tmpfs can be mounted also while users are logged (I guess not or you would have to mv relevant files with all the connected problems) anyways situation is as follows: I logged in and worked until I started having usual /tmp full problems because the ramfs has a fixed size.

We must be sure that user is warned to reboot as soon as possible when the ramfs is mounted, and the fake device name of the ramfs (tmpfs, whatever) should be the name of a readme file explaining what happened. If I had not followed the thing from the beginning here, I would never have understood who had mounted that tmpfs, which I saw using "df".

Maybe I didn't get a warning because I have autologin and login arrived _before_ tmpfs being mounted?