On 7/31/12 4:38 PM, Theodore Ts'o wrote: > On Tue, Jul 31, 2012 at 04:54:42AM +0000, Nelson, John R wrote: >> ok i am using 3.2.0-27-generic (ubuntu 64 bit) e2fsporgs 1.42. the filesystem is 681GB. Both computers are intel based on is core i5 and one is intel atom and they are in no special configuration just one sata cable to each drive >> >> here are the steps i did >> 1. fallocate file1 -l 500gb << exact method >> 2.mkfs.ext4 file1 << exact method >> i will get the error messages about it failing, i delete the file and fsck is still forced upon next mount > > OK, I see what's going on. I was able to reproduce it using a 3.2 > kernel (but not a more recent kernel which is what I normally use; > more about that later) with a slightly smaller size (since that's all > the space I had on free on my laptop): > > # fallocate -l 215g file1 > # mke2fs -t ext4 -F file1 > > The problem is that fallocate allocated a large number of blocks, which > mke2fs then immediately discarded as its first order of business. Hm, then why didn't mkfs.ext4 -K solve the problem.... -Eric -- 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
