public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
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 17:41:09 -0400	[thread overview]
Message-ID: <20170623214109.3kwtxj3owi4noxda@thunk.org> (raw)
In-Reply-To: <087C00FA-AF13-498F-8D6A-B67A115D8DCE@dilger.ca>

On Fri, Jun 09, 2017 at 03:00:56PM -0600, Andreas Dilger wrote:
> 
> 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).

Also, does Lustre use large_dir on the MDS server, or on the Lustre
data server?  Because I noticed that on the MDS server you're
apparently not using extents:

export EXT_MKFS_OPTIONS="-I 2048 -O ^64bit,mmp,uninit_bg,^extents,dir_nlink,...
                                                         ^^^^^^^^

Are you really using large_dir on a file system that is using indirect
block mapped files?

						- Ted

  reply	other threads:[~2017-06-23 21:41 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 [this message]
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=20170623214109.3kwtxj3owi4noxda@thunk.org \
    --to=tytso@mit.edu \
    --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