Hello, > On Wed, 2006-10-11 12:42:02 +0200, Jan Kara <jack@xxxxxxx> wrote: > > > On Sun, 2006-10-08 08:33:30 +0200, Jan-Benedict Glaw <jbglaw@xxxxxxxxxx> wrote: > > > While I could reproduce it with a 200MB file, it seems I can't break > > > it with a 10MB file. > > Hmm, I was running the test for several ours without any problem... > > The kernel is 2.6.17.6, ext3 in ordered data mode, standard SATA disk. I'm > > now running it again and trying my luck ;). What is your testing environment? > > kolbe34-backup:/mnt# uname -a Thanks for info. This looks pretty similar to what I have (only that I have Athlon). > Still running Debian's 2.6.17-2-686, I'm now tracking down the file > size when I start to see this type of corruption. Right now, it seems > I never get it with a 16384 KB (16 MB) large file, but I get it with a > 21504 KB (21 MB) file. > > Is there something important that changes handling of file contents in > the 16..21 MB range? Umm, I've checked and found nothing obvious. We already have to use double-indirect block at 16MB, maybe reservation code does some distiction. Could you mount the filesystem with -o 'noreservation' and see whether you can still reproduce the problem? Also it may be useful to find out, whether you see the failure also with some older kernels... Honza > > dumpe2fs output at http://lug-owl.de/~jbglaw/ext3-dumpe2fs.txt for > that filesystem. I'll now run with a 18.5 MB file... > > MfG, JBG > > -- > Jan-Benedict Glaw jbglaw@xxxxxxxxxx +49-172-7608481 > Signature of: Wenn ich wach bin, träume ich. > the second : -- Jan Kara <jack@xxxxxxx> SuSE CR Labs - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
