Quote:
Originally Posted by knc1
That df listing looks a lot like you are running the "diags" partition (which you should be, if intending to update the "main" partition).
Your machine is a "dual boot" machine. The two system are not the same, nor even close to the same size.
Try instead:
cat /proc/partitions
Which will show kernel recognized partitions (as devices) even if not mounted.
- - - -
The usual cause of filling up /var/local (which is the file system on /dev/mmcblk0p3) is book indexes (indices). Index fewer books. The "too small" /dev/mmcblk0p3 partition was a lab126 design decision.
- - - -
Your NAS can probably be put back into service, but you will probably need a to use the serial (kernel operator console) port to do it.
Plus, on something that "runs forever" your syslog configuration and log rotation configuration needs to be setup for that usage so that the current fill-up does not happen.
You should also suspect something different or additional wrong with your NAS - lack of space for log files (or even utmp) should not prevent it from booting.
|
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.