From: Andreas Dilger <adilger@dilger.ca>
To: Theodore Ts'o <tytso@mit.edu>
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, 9 Jun 2017 15:00:56 -0600 [thread overview]
Message-ID: <087C00FA-AF13-498F-8D6A-B67A115D8DCE@dilger.ca> (raw)
In-Reply-To: <20170609175910.shwqocbi3npfmoid@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Jun 9, 2017, at 11:59 AM, Theodore Ts'o <tytso@mit.edu> wrote:
>
> On Fri, Jun 09, 2017 at 11:55:56AM +0300, Artem Blagodarenko wrote:
>> Hello Theodore,
>>
>> Is it good time to add large_dir feature to this configuration?
>
> Andreas didn't include large_dir on the list of features that he
> enabled; what's the status of use of that feature by Lustre system in
> production?
I didn't include large_dir because it isn't included in the upstream
kernels yet, and we haven't been using this in production due to lack
of e2fsck support (which Seagate has finally implemented, thank you).
By all means, I'm in favour of adding this feature to the testing matrix.
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-06-09 21:01 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 [this message]
2017-06-23 21:41 ` Theodore Ts'o
2017-06-23 22:00 ` Andreas Dilger
2017-06-23 23:08 ` 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=087C00FA-AF13-498F-8D6A-B67A115D8DCE@dilger.ca \
--to=adilger@dilger.ca \
--cc=artem.blagodarenko@seagate.com \
--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