From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: Reiser4 crash 2.6.16-mm1 Date: Tue, 28 Mar 2006 13:04:38 -0800 Message-ID: <4429A4E6.5000202@namesys.com> References: <20060327214132.4074.qmail@pv105234.reshsg.uci.edu> <20060327223214.5291.qmail@pv105234.reshsg.uci.edu> <200603280439.k2S4dAql011014@turing-police.cc.vt.edu> <4429577C.7020105@ics.uci.edu> <1143573487.2380.1.camel@localhost> <20060328205021.3873.qmail@pv105234.reshsg.uci.edu> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20060328205021.3873.qmail@pv105234.reshsg.uci.edu> List-Id: Content-Type: text/plain; charset="us-ascii" To: Joe Feise , vs Cc: Jonathan Briggs , reiserfs-list@namesys.com Joe Feise wrote: > Jonathan Briggs writes: > >> 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 > > > Indeed, it does. Dell gets that right on server machines, at least... > I have now recreated the fs on that partition, and played the data > back from backup, and it works fine. I have made a copy of the old > partition with dd, to be able to run some more tests when I have time. > -Joe > > Well, if it is ECC RAM, then we should probably assume it is a bug. Sigh. Vs, can you look at it?