From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Nelson, John R" <John_Nelson@student.uml.edu>,
linux-ext4@vger.kernel.org
Subject: Re: Serious bug?
Date: Tue, 31 Jul 2012 16:40:36 -0500 [thread overview]
Message-ID: <501850D4.8060101@redhat.com> (raw)
In-Reply-To: <20120731213845.GA3945@thunk.org>
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
next prev parent reply other threads:[~2012-07-31 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 2:17 Serious bug? Nelson, John R
2012-07-31 2:29 ` Eric Sandeen
2012-07-31 2:42 ` Theodore Ts'o
[not found] ` <0408C81F72528E40A0D3235A1F67FFC804A643@SN2PRD0202MB144.namprd02.prod.outlook.com>
[not found] ` <20120731032536.GE5027@thunk.org>
[not found] ` <0408C81F72528E40A0D3235A1F67FFC804A65F@SN2PRD0202MB144.namprd02.prod.outlook.com>
2012-07-31 21:38 ` Theodore Ts'o
2012-07-31 21:40 ` Eric Sandeen [this message]
2012-07-31 22:34 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501850D4.8060101@redhat.com \
--to=sandeen@redhat.com \
--cc=John_Nelson@student.uml.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).