From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: mkfs'ing a 48-bit fs... or not.
Date: Mon, 03 Oct 2011 23:03:40 -0500 [thread overview]
Message-ID: <4E8A859C.2070501@redhat.com> (raw)
In-Reply-To: <4E8A2F3F.30700@sandeen.net>
On 10/3/11 4:55 PM, Eric Sandeen wrote:
> Has anyone tried mke2fs at its limits? The latest git tree seems to fail in several ways.
> (Richard Jones reported the initial failure)
>
> # truncate --size 1152921504606846976 reallybigfile
> # mke2fs -t ext4 reallybigfile
...
> Trying it with "-O bigalloc" (which should be automatic at this size,
> I think?) just goes away for a very long time, I'm not sure what it's
> thinking about, or if it's in a loop somewhere (looking now).
It comes up with too many inodes, then tries to reduce the count,
but the "waste not want not" logic bumps it back up... ipg eventually
goes "below" 0 but it's unsigned so it goes on in this loop forever.
Some of this is my fault... I put that retry logic in years ago. :(
I'll see what I can do to fix it up.
-Eric
next prev parent reply other threads:[~2011-10-04 4:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 21:55 mkfs'ing a 48-bit fs... or not Eric Sandeen
2011-10-04 4:00 ` Ted Ts'o
2011-10-04 4:26 ` [PATCH 1/2] Add "big" and "huge" types to mke2fs.conf Theodore Ts'o
2011-10-04 4:27 ` [PATCH 2/2] libext2fs: fix bad cast which causes problems for file systems > 512EB Theodore Ts'o
2011-10-04 11:47 ` Eric Sandeen
2011-10-04 18:05 ` Ted Ts'o
2011-10-04 18:15 ` Eric Sandeen
2011-10-04 5:31 ` mkfs'ing a 48-bit fs... or not Andreas Dilger
2011-10-04 4:03 ` Eric Sandeen [this message]
2011-10-04 4:28 ` Ted Ts'o
2011-10-04 7:06 ` Richard W.M. Jones
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=4E8A859C.2070501@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).