Incorrect Free Disk Space using df -k

Incorrect Free Disk Space using df -k

Post by Mart » Thu, 02 May 2002 09:26:51



I have a 64MB /var fileset using the AdvFS filesystem.
The CRON log file filled the filesystem and the /var volume ran out of
disk space.

I have moved the log file to another volume, and the 64MB /var volume
now only has 8MB used.  However, the system returns a full filesystem
on /var when I issue a df-k.

Because the system thinks the filesystem is full, there is no swap /
tmp area for CRON or mail, so the system will not function.

Is there a way of updating the free disk space for a volume without
rebooting the server?

Marty

 
 
 

Incorrect Free Disk Space using df -k

Post by Bob Harri » Thu, 02 May 2002 22:20:05



X I have a 64MB /var fileset using the AdvFS filesystem.
X The CRON log file filled the filesystem and the /var volume ran out of
X disk space.
X
X I have moved the log file to another volume, and the 64MB /var volume
X now only has 8MB used.  However, the system returns a full filesystem
X on /var when I issue a df-k.
X
X Because the system thinks the filesystem is full, there is no swap /
X tmp area for CRON or mail, so the system will not function.
X
X Is there a way of updating the free disk space for a volume without
X rebooting the server?
X
X Marty

Run quotacheck.  That should get things more in line with reality.

                                        Bob Harris

 
 
 

Incorrect Free Disk Space using df -k

Post by Bob Harri » Thu, 02 May 2002 22:22:51



X I have a 64MB /var fileset using the AdvFS filesystem.
X The CRON log file filled the filesystem and the /var volume ran out of
X disk space.
X
X I have moved the log file to another volume, and the 64MB /var volume
X now only has 8MB used.  However, the system returns a full filesystem
X on /var when I issue a df-k.
X
X Because the system thinks the filesystem is full, there is no swap /
X tmp area for CRON or mail, so the system will not function.
X
X Is there a way of updating the free disk space for a volume without
X rebooting the server?
X
X Marty

I should have also said that _IF_ any process still has the log open,
then the log will not be deleted until the last process closes the file.

fuser may help identify if there are any processes that still have the
file open, or the freeware lsof utility.

                                        Bob Harris