Re: 2.4.22-rc2 ext2 filesystem corruption

[Marcelo Tosatti <marcelo@conectiva.com.br>]

On Tue, 12 Aug 2003, Martin Maney wrote:

> On Tue, Aug 12, 2003 at 10:12:19AM -0300, Marcelo Tosatti wrote:
> > Can you tell me exactly how can I try to reproduce the problem you're 
> > seeing? 
> > 
> > With just cp and unmount you can see the corruption? 
> 
> Yes.  With the c. 50MB file it happens every time (now out of a couple
> dozen tests).  A 3MB file did not get corrupted in half a dozen trials,
> including ones where both were copied before the umount.
> 
> The age & condition of the target filesystem don't seem to matter; at
> least I have replicated this immediately following mke2fs of the
> target.  The original observed corruption was on much older and more
> cluttered filesystems - the first sign of trouble was when a local
> build of XFree failed.
> 
> In case I wasn't perfectly clear (it was late, so that may well be), I
> used the umount/mount only to invalidate the buffers; merely syncing
> after copying wouldn't produce any immediate effect.  The copy always
> looks good until the data has to be read back from the target
> filesystem.
> 
> One other item which I didn't think to mention is that the compiler was
> "gcc version 2.95.4 20011002" - Debian's normal compiler in the Woody
> release.  Of course that's been used for every other 2.4 kernel I've
> built here as well.

I'll try to reproduce around here. In the meantime can you try to isolate 
the corruption. You said it didnt happen with 2.4.21 -- which pre shows up 
the problem?