Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No space left on device?

Status
Not open for further replies.

inetd

Technical User
Jan 23, 2002
115
HK

I have received a mail from logwatch like this:

--------------------- Cron Begin ------------------------

**Unmatched Entries**
DEATH (can't open or create /var/run/crond.pid: No space left on device)

---------------------- Cron End -------------------------



------------------ Disk Space --------------------

Filesystem Size Used Avail Use% Mounted on
/dev/hda2 981M 197M 734M 22% /
/dev/hda1 99M 24M 70M 26% /boot
/dev/hda6 981M 121M 811M 13% /home
none 188M 0 188M 0% /dev/shm
/dev/hda9 449M 9.7M 416M 3% /tmp
/dev/hda5 2.9G 1.9G 914M 68% /usr
/dev/hda8 981M 277M 655M 30% /usr/local
/dev/hda7 981M 312M 620M 34% /var
/dev/hdc1 13G 438M 12G 4% /mnt/data


Is it said that it has "No space left on device" on /var?
However the df say that /var has 620M available.

Pls help.
Thanks.

 
Perhaps the job reaches the limit and then backs out, deleting whatever it's produced in the meantime and thus releasing diskspace back, rather like a failed compression.
 
Are you using an RAID array.

My experience with similiar issues like this was due to a filing drive within the RAID array.
 
Also try a `df -i` to check inodes in /var
 
Is /var/run softlinked to another filesystem maybe ?
Have you tried creating the file manually ?

touch /var/run/crond.pid
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top