From: Andreas Dilger <adilger@sun.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: [E2FSPROGS, RFC] New mke2fs types parsing
Date: Thu, 21 Feb 2008 01:52:21 -0700 [thread overview]
Message-ID: <20080221085221.GV3029@webber.adilger.int> (raw)
In-Reply-To: <20080220222019.GG30305@mit.edu>
On Feb 20, 2008 17:20 -0500, Theodore Ts'o wrote:
> There are only three things which mke2fs will do, in my design:
This should all go into the mke2fs man page...
> [fs_types]
> ext3 = {
> features = has_journal
> }
> ext4 = {
> features = extents,flex_bg
> inode_size = 256
> }
Presumably the ext4 feature should also have features = has_journal?
If this is the default for ext4, why would it need to be given for ext3?
We should also add "dir_nlink,flexbg" while we are in there.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-02-21 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 14:06 [E2FSPROGS, RFC] New mke2fs types parsing Theodore Ts'o
2008-02-20 18:51 ` Eric Sandeen
2008-02-20 22:20 ` Theodore Tso
2008-02-20 22:28 ` Eric Sandeen
2008-02-21 8:52 ` Andreas Dilger [this message]
2008-02-21 13:35 ` Theodore Tso
2008-03-17 21:29 ` Eric Sandeen
2008-03-18 2:20 ` Theodore Tso
2008-03-18 3:23 ` Eric Sandeen
2008-03-18 4:23 ` Theodore Tso
2008-03-18 5:16 ` Eric Sandeen
2008-03-18 11:01 ` Theodore Tso
2008-03-18 13:11 ` Eric Sandeen
2008-03-18 13:52 ` Theodore Tso
2008-03-18 16:06 ` Eric Sandeen
2008-03-20 19:17 ` Eric Sandeen
2008-03-20 20:49 ` Theodore Tso
2008-03-19 3:36 ` Andreas Dilger
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=20080221085221.GV3029@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.