Re: [cobalt-users] EXT2-fs warning ext2_free_inode

["H.P. Stroebel" <hpstr@xxxxxxxxxxxxx>]

> Zeffie schrieb:

> I am now getting this error message on a regular basis
> Aug  5 05:18:01 www kernel: EXT2-fs warning (device 03:04): ext2_free_inode:
> bit already cleared for inode 28673

as this seems strange and i am interested in the solution, i looked a
bit around :

a) seems to be common, lots of similar questions.

b) interesting :  did you compile something ? did you upgrade memory ?
and what memory did you use ? could be a (bad) ram problem. did you
upgrade your hdd ? other reasons could be high cpu temp, disk i/o errors
etc.

maybe you should do as soon as possible a full backup, and then run
fsck.

c) it is also reportet for some redhat (!) installations, even if
everything goes right.

read
http://download.sourceforge.net/mirrors/slackware/slackware/docs/faqs/GCC-SIG11-FAQ
:

*****
QUESTION
Is it always signal 11?
ANSWER
Nope. Other signals like four, six and seven also occur occasionally.
Signal 11 is most common though.
As long as memory is getting corrupted, anything can happen. I'd expect
bad binaries to occur much more often than they really do. Anyway, it
seems that the odds are heavily biased towards gcc getting a signal 11.
Also seen:
(...)
EXT2-fs warning (device 08:14): ext_2_free_blocks bit already cleared
for block 127916
(...)

The first few ones are cases where the kernel "suspects" a
kernel-programming-error that is actually caused by the bad memory. The
last few point to application programs that end up with the trouble.

*****





-- 

H. P.  Stroebel, Germany

CGI-FAQ for Raq-Newbies :
http://users.iol.it/hpstr/

A problem to some is a 'feature' to others.