xfs
[Top] [All Lists]

Re: Corruption of in-memory data detected.

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Corruption of in-memory data detected.
From: Utz Lehmann <ulehmann@xxxxxxxxxxxxxx>
Date: Thu, 25 Oct 2001 17:39:09 +0200
Cc: "Martin K. Petersen" <mkp@xxxxxxx>, Utz Lehmann <ulehmann@xxxxxxxxxxxxxx>, Marc Schmitt <schmitt@xxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx, florin@xxxxxxx
In-reply-to: <200110251505.f9PF5De15624@xxxxxxxxxxxxxxxxxxxx>; from lord@xxxxxxx on Thu, Oct 25, 2001 at 10:05:13AM -0500
References: <mkp@xxxxxxx> <200110251505.f9PF5De15624@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.12i
Steve Lord [lord@xxxxxxx] wrote:
> > >>>>> "Steve" == Steve Lord <lord@xxxxxxx> writes:
> > 
> > Steve> Ah ha, now thats a good idea - of course I still think its the
> > Steve> md code, but at least we have a chance of catching it now.
> > 
> > I took a look at MD last night and didn't see anything obvious
> > sticking out.
> > 
> > Will do a second pass in a bit...
> > 
> > -- 
> > Martin K. Petersen      Cereal Bowl Engineer, Linuxcare, Inc.
> > http://mkp.net/         SGI XFS, Linux/PA-RISC, GNOME
> 
> Martin, forget md, you can make this happen without it, looks like we 
> introduced a sign bug ourselves somewhere.... I just toasted the loop
> based filesystem in about 10 seconds. Hopefully with a case this 
> simple to reproduce it should not take long now.

Is the loop device unsign safe?


utz


<Prev in Thread] Current Thread [Next in Thread>