From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>, G@thunk.org
Cc: Artem Blagodarenko <artem.blagodarenko@seagate.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] test-appliance: add new test configuration: ext4/lustre_mds
Date: Fri, 23 Jun 2017 19:08:19 -0400 [thread overview]
Message-ID: <20170623230819.r5j63cmdb5aafdc2@thunk.org> (raw)
In-Reply-To: <3625058A-4B6D-4C28-B231-61DFED33F0B4@dilger.ca>
On Fri, Jun 23, 2017 at 04:00:05PM -0600, Andreas Dilger wrote:
> > Are you really using large_dir on a file system that is using indirect
> > block mapped files?
>
> Like I wrote above, we haven't been using large_dir in production yet.
> My plan was only to use it on the MDT, which is where the filesystem
> namespace is located. Indeed, we don't use extents on the MDT because:
> a) ext4 MDTs are strictly less than 16TB in size (usually < 8TB, even with
> 4B inodes) because of using "-I 2048" to limit the space per inode,
> so they never need more than 2^32 blocks
> b) the only files of any size on the MDT are directories or other log
> files, which are rarely created with contiguous block allocations,
> so extents usually take more space than indirect blocks (12 bytes vs 4).
OK, I'll try adding large_dir to the luster_mds configuration. I'm
not sure we're actually going to end up creating a directory with 3
levels of htree nodes, though. In order to force that we'll probably
need to create a new ext4-specific htree stress tester which creates a
large number of filenames that very long, preferably while using a 1k
block file system.
- Ted
prev parent reply other threads:[~2017-06-23 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 3:59 [PATCH] test-appliance: add new test configuration: ext4/lustre_mds Theodore Ts'o
[not found] ` <CAO3qy=EVQtVVe2hvEvaYOTyArPpK7U6AYA9abu6Zum-p_sWqpg@mail.gmail.com>
2017-06-09 17:59 ` Theodore Ts'o
2017-06-09 21:00 ` Andreas Dilger
2017-06-23 21:41 ` Theodore Ts'o
2017-06-23 22:00 ` Andreas Dilger
2017-06-23 23:08 ` Theodore Ts'o [this message]
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=20170623230819.r5j63cmdb5aafdc2@thunk.org \
--to=tytso@mit.edu \
--cc=G@thunk.org \
--cc=adilger@dilger.ca \
--cc=artem.blagodarenko@seagate.com \
--cc=linux-ext4@vger.kernel.org \
/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