From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernd Schubert <bernd-schubert@web.de>
Subject: Re: filesystem corruption ?
Date: Sat, 22 Mar 2003 19:18:23 +0100
Sender: bernd-schubert@web.de
Message-ID: <200303221918.23552.bernd-schubert@web.de>
References: <200303201725.14039.bernd-schubert@web.de> <20030321103230.C12315@namesys.com> <200303211401.38329.bernd-schubert@web.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-13332-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <200303211401.38329.bernd-schubert@web.de>
Content-Disposition: inline
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com

Hello,

> Though this machine will be replaced by a real server in a few month, I'm
> still rather worried what happend. Even if its 'only' a hardware memory
> problem this means lots of trouble for us -- on the one hand it seems not
> to be memtest86 detectable and on the other hand our programs really do
> need working memory, but of course this is not of your concern.

Update: I yesterday started our fall-back-server and run another memtest86 on 
the suspected machine. A colleague just told me that memtest86 reported 3 
errors in test 8, well lets see what comes in test 11.
So this either means that the physicians have run some experiments today or 
that the memory became damaged within 2 weeks.

Thanks a lot for your help to identify this as a hardware problem.

Best regards,
	Bernd