Messages in this thread | | | Date | Tue, 12 Aug 2003 10:12:19 -0300 (BRT) | From | Marcelo Tosatti <> | Subject | Re: 2.4.22-rc2 ext2 filesystem corruption |
| |
On Mon, 11 Aug 2003, Martin Maney wrote:
> The recipie is simple: cp a large file across filesystems. All looks > well (md5sums match, etc), but the file is all still present in memory. > But if you then unmount the destination filesystem to invalidate the > buffers, after mounting the file data will have changed. I'm pretty > certain that I have observed the same effect without the mass > invalidation of umount in a couple of cases, but I haven't replicated > that. > > In all cases I have investigated, the corruption seems to take the form > of four bytes of garbage at the beginning of a block; two small scripts > have been observed with 4 NULLs prepended and the last four characters > truncated. In another case I found a block of over 100 bytes (I got > tired of wading through it after a while) in the same form - four bytes > were inserted into the corrupted file, pushing the data back. In > hindsight I wish I had investigated that case further; as it is, I'm > not positive the dislocation was at a disk block boundary.
Martin,
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?
- 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/
| |