lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 31 Jul 2012 16:40:36 -0500
From:	Eric Sandeen <>
To:	"Theodore Ts'o" <>
CC:	"Nelson, John R" <>,
Subject: Re: Serious bug?

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....

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists