Date: Thu, 15 Jan 2004 15:42:41 +0300
Message-ID: <87smihxu0u.wl@canopus.ns.zel.ru>
From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: Ville Herva <vherva@twilight.cs.hut.fi>,
       Samium Gromoff <deepfire@sic-elvis.zel.ru>,
       linux-kernel@vger.kernel.org
Subject: Re: Something corrupts raid5 disks slightly during reboot
In-Reply-To: <20040114223040.GV11115822@niksula.cs.hut.fi>
References: <877jzuxz5i.wl@canopus.ns.zel.ru>
	<20040114223040.GV11115822@niksula.cs.hut.fi>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 812
Lines: 26

At Thu, 15 Jan 2004 00:30:40 +0200,
Ville Herva wrote:
> 
> On Wed, Jan 14, 2004 at 07:39:37PM +0300, you [Samium Gromoff] wrote:
> > 
> > I know this sounds stupid, but anyway:
> > 
> > I have seen the very same symptome caused by RAM faults (too slow ram
> > for given clocks, to be exact).
> 
> The very same? You mean if booted, wrote few kB's of data to disk, synced,
> then pressed reset, the same three bytes were corrupted (set to zero) each
> time after reboot? 

No, corruption after reboot and perfect work inbetween.

> v@iki.fi

regards, Samium Gromoff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/