[plug] File System Errors - Take II

[Steve Grasso]

Sorry, my previous was probably a bit brief. To verify inode or space on 
partitions:

df -hi 

will tell you your inode status for each partition while

df -h

will tell you your diskspace allocation/availability for each partition.

Generally, with respect to /var if you're short on inodes, but have tons of 
free space, suspect miriads of small files (eg. error messages sent to root - 
either fix the thing(s) generating the messages, or clear out the messages 
periodically). If you're short on space but have tons of inodes, suspect huge 
logs. Similarly, check the logs to find the source of messages & fix that, or 
move/clear old logs periodically.

Regards,
Steve

On Friday 17 August 2001 15:48, Steve Grasso wrote:
> Andrew,
>
> This sounds more like the /var partition either running out of inodes or
> diskspace. My suggestion for a quick-fix would be to set up a cron job to
> periodically move old log files to another partition/machine, or delete
> them, and to check in /var/spool/mqueue for runaway error messages to root.
> Set up a cron to move or clear these out also.
>
> Regards,
> Steve
>
> On Friday 17 August 2001 15:51, Andrew Barbara wrote:
> > Hi,
> > One of our client's linux RedHat 7.1 server is Jamming up.  When I
> > Re-Boot it takes me to a file system repair shell, I run fsck on the
> > troubled file system (/var) and reboot then all is fine for a couple of
> > weeks.  This is the second time its happened.  Is it a faulty Hard Drive?
> > Or a linux issue?
> >
> > Thanks
> > Andrew Barbara