Hans Reiser writes:
Jonathan Briggs wrote:
On Tue, 2006-03-28 at 07:34 -0800, Joachim Feise wrote:
[...]
This is a production machine that I can't take offline for too long.
But yes, I have compiled the kernel on another reiser4 partition over night,
without problems.
If this was a memory problem, it would indeed manifest itself in other areas
with more or less random errors. The fact that it does not indicates to me that
this is a fs problem. So, at this point I am ruling out a memory issue.
And if it's a production machine, it is using ECC RAM, I would hope. If
it is, memory problems (unreported ones, anyway) are very, very
unlikely.
Jonathan, be merciful, ECC ram last I checked is twice the cost of
regular and the mobs cost more too. (I am sure the cost to produce is <
15% more, which makes it a great pity Intel does not standardize on
requiring it and force it to be cheap) Some folks need to save money.
Yeah, I know, this time it may have cost him more in cost of his time
but we are all just assuming it is memory. Unfortunately, unless he
checks it or we see an identical error message from another user with
checked memory, or vs tells me he sees a flaw in the code, we need to
assume it is memory.
The machine is using ECC memory. Geez, I know what I need for a server...
From the Dell invoice:
512MB DDR2, 400MHz,2X256MB ECC 1R DIMMs for PowerEdge SC420
Recreating the partition solved the problem. So to me it sure looks like fs
corruption.
I have sent the dmesg output earlier.
-Joe
