NSLU2-Linux
view · edit · print · history

Extracts taken from http://groups.yahoo.com/group/nslu2-linux/message/1493 by peecock41

The box beeps every 8 hours for about a minute, each time three short beeps. Looking into /var/log/server.log I found the following:

  • 09/17 08:00:00 Disk 1 is almost full. Continued use will affect file access.

I haven't found this in the manual, but there you go. Indeed I filled filled up my disk already. Here's the system status log, as you can see, the disk full check is run at 00:00, 08:00, and 16:00.

  • 09/18 08:00:00 Disk 1 is almost full. Continued use will affect file access.
  • 09/18 00:00:00 Disk 1 is almost full. Continued use will affect file access.
  • 09/17 16:00:00 Disk 1 is almost full. Continued use will affect file access.
  • 09/17 08:00:00 Disk 1 is almost full. Continued use will affect file access.
  • 09/17 00:00:39 Disk 1 is almost full. Continued use will affect file access.

It is actually the cronjob defined in /etc/crontab doing this:

0 0-23/8 * * * root /usr/sbin/CheckDiskFull &>/dev/null

where at 0 minutes, every 8th hour between 0 and 23 hour, at every day month year, the command /usr/sbin/CheckDiskFull is executed, all output going into the bitbucket and discarded.

Note: As this has been asked many times. It beeps when 98% of your disk is full, so the bigger the disk, the more space there is still left (as it is checked in PERCENTAGE full, not absolute Gbytes).


References

http://groups.yahoo.com/group/nslu2-linux/message/1493 http://groups.yahoo.com/group/nslu2-linux/message/1538

view · edit · print · history · Last edited by MattMcN.
Originally by peecock41.
Page last modified on April 14, 2005, at 10:26 PM