File System Error

wolf-r1 · 12-10-2006, 10:39 AM

Hello,

I have a machine that's reporting the following error:

Quote:

inode0x4801: 10673261 at c5ebf200: mode 100644, nlink 2, next 0

It is not responsive via network and is at a data center to which I am about to go to so that I can investigate further what's wrong with this machine.

Anyone have any advice to what I should be looking for? I've never had to investigate file system errors on a Linux machine before.

OS is RHL 7.3

Thanks.

trickykid · 12-10-2006, 12:29 PM

Could be anything really. My only advice is try running fsck on the drive upon a reboot or the like. Could be a failed drive even, you'll definitely know once you're at the machine though.

wolf-r1 · 12-10-2006, 02:11 PM

Thanks. On reboot the machine ran fsck on it's own and that seemed to fix the problem. It was repeating that error thousands of times a second though which was odd.

trickykid · 12-10-2006, 02:54 PM

Quote:

Originally Posted by wolf-r1

Thanks. On reboot the machine ran fsck on it's own and that seemed to fix the problem. It was repeating that error thousands of times a second though which was odd.

Filesystem errors do generate a lot of repeated errors in the logs.

wolf-r1 · 12-10-2006, 09:03 PM

Thanks for that info. That helps to know though this seemed to be an unending loop of that same error message over and over again until I shut the machine down and it ran the fsck automatically.

matthewg42 · 12-10-2006, 09:16 PM

It might be an idea to check your logs regularly for a little while. If the drive if getting bad sectors, it might cascade... keep an eye on it. Oh, and do a full backup ASAP.