From: Andreas Dilger <adilger@sun.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC V3] ext4: limit block allocations for indirect-block files to < 2^32
Date: Fri, 11 Sep 2009 00:01:00 +0200 [thread overview]
Message-ID: <20090910220100.GK9372@webber.adilger.int> (raw)
In-Reply-To: <20090910215158.GI9372@webber.adilger.int>
On Sep 10, 2009 23:51 +0200, Andreas Dilger wrote:
> Well, it may depend a lot on which inodes are in use. That will set the
> goal block, and may prevent any above-16TB allocations. Either you could
> fill the bitmaps with 0xff (and zero the free blocks counters, to avoid
> problems with mballoc), or actually fill the first 16TB of the filesystem.
Or, just start creating top-level directories until you get one past
16TB and use that for your test... We have a patch for allowing a
goal inode to be specified, and it might make sense to add a mount
option to allow setting the inode goal for testing...
Hey, look, I even posted that patch, I now recall:
http://osdir.com/ml/linux-ext4/2009-06/msg00233.html
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-09-10 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 22:17 [PATCH, RFC] ext4: limit block allocations for indirect-block files to < 2^32 Eric Sandeen
2009-09-05 3:21 ` [PATCH, RFC V2] " Eric Sandeen
2009-09-05 16:45 ` Andreas Dilger
2009-09-05 18:16 ` Eric Sandeen
2009-09-10 16:02 ` [PATCH, RFC V3] " Eric Sandeen
2009-09-10 16:53 ` Theodore Tso
2009-09-10 16:56 ` Eric Sandeen
2009-09-10 21:10 ` Andreas Dilger
2009-09-10 21:16 ` Eric Sandeen
2009-09-10 21:33 ` Theodore Tso
2009-09-10 21:42 ` Eric Sandeen
2009-09-10 21:51 ` Andreas Dilger
2009-09-10 21:57 ` Eric Sandeen
2009-09-10 23:19 ` Theodore Tso
2009-09-11 14:15 ` Eric Sandeen
2009-09-10 22:01 ` Andreas Dilger [this message]
2009-09-14 20:03 ` [PATCH, RFC V4] " Eric Sandeen
2009-09-16 18:54 ` Theodore Tso
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=20090910220100.GK9372@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).