On Sat, Mar 24, 2001 at 11:41:38PM -0800, Tim Uckun wrote: > > Now any idea what this could mean? I am pretty sure a cron job is spitting > out these errors into the log but what cron job and why? > > iput: device 03:01 inode 110047 still has aliases! > iput: device 03:01 inode 65988 still has aliases! > iput: device 03:01 inode 112902 still has aliases! > iput: device 03:01 inode 141716 still has aliases! > iput: device 03:01 inode 142142 still has aliases! > iput: device 03:01 inode 94274 still has aliases! > iput: device 03:01 inode 96020 still has aliases! > iput: device 03:01 inode 156730 still has aliases! > > There are a TON of these.
My first guess would be filesystem errors... Did you try 'fsck'? This may be the result of a large number of file deletions recently. On my system cron job STDOUT and STDERR gets emailed to me. I would think that maybe the system is trying to free these inodes back for use, but can't. Take the system to single user and run fsck to see what happens. ->W -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Wesley Wannemacher Instructor / Network Administrator University of Northwestern Ohio http://www.unoh.edu/ [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It is my job in life to travel all roads, so that some may take the road less travelled, and others the road more travelled, and all have a pleasant day. -- Larry Wall in <[EMAIL PROTECTED]>
