We've
been seeing some very unusual behavior in linuxconf of late. When using
linuxconf through a telnet terminal session, the techs usually activate the
changes when they're finished. When activating the changes, the session appears
to lock up. When you go and look at the console, it displays a continuous
message: "VFS: out of inodes. Contact Linus." That's a pretty serious
error! The machine won't respond at that point so a hard boot is required. After
any necessary fsck'ing the drive, everything's back to normal. Looking at the
filesystem's inode usage shows that there are still over a million inodes left.
Something is strange here.
Any
ideas?
Sean Stoner
HYPERCON, INC.
"Internet Solutions that
make Sense"
http://www.hypercon.com
2024 Bissonnet St.
Houston, TX
77005
713-528-2400
