Quote:
Originally Posted by rynax
Hi, thanks for the reply.
Yes, the df listing is result from diags mode via ssh.
The NAS, was caused by that it has 0 byte left on the disk, I took out the drive, hooked it to another machine, cleared out some logs and it booted ok. Some errors filled out the logs very quickly. Yes configuration the log could prevent it from filling up the drive. But it is true Linux will brick if there's no space left? See the Kindle and the NAS.
|
Depends on your file system and file system options.
It is also not restricted to Linux, any **disk based** operating system will "brick" if it runs out of disk space. ANY!
Linux, true to its heritage of Unix, "boots" (actually, system IPL) under the supervisor's username 'root'.
Any *nix related file system will have an area (percentage) of disk space reserved for 'root', so that the username 'root' can recover the system from "out of disk space" situations.
The system administrator (You) can defeat this by:
Running everything as the supervisor 'root' -
Optioning the file system so that space is not reserved for 'root' -
Running the system with a non-*nix file system (which does not implement the concept of a 'reserved area').
A for simple instance of #1 :
lab126 implemented the Kindle system with nearly everything running as username 'root' (a really bad idea) (tm) ;
Many other embedded linux systems make the same (simplistic) choice, likely to be the root (no pun intended) of your NAS problems.
If you don't believe that above ANY!
Fill up the entire disk of your M$-Windows box, see how long it lasts; no cheating, don't allow a dynamically sized swap file/disk.