From: Mingming Cao <cmm@us.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Valerie Clement <valerie.clement@bull.net>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH 3/8][e2fsprogs] add new -D <desc-size> option to mkfs
Date: Fri, 31 Aug 2007 17:25:00 -0700 [thread overview]
Message-ID: <1188606300.15123.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20070830205145.GK5377@schatzie.adilger.int>
On Thu, 2007-08-30 at 14:51 -0600, Andreas Dilger wrote:
> On Aug 30, 2007 12:12 -0700, Mingming Cao wrote:
> > On Thu, 2007-08-30 at 17:37 +0200, Valerie Clement wrote:
> > > This patch adds a new option -D <descriptor-size> to mkfs to allow creating
> > > ext4 filesystems with larger group descriptor size.
> > >
> > > By default, the group descriptor size is 32 bytes.
> > > To support 64-bit physical block numbers and thus to be able to use filesystems
> > > > 16TB, the group descriptor size must be increased to 64 bytes.
> >
> > Could you explain a bit more why we need this option? It seems to me we
> > could make the block group descriptor size to 64bytes whenever creating
> > a ext4 filesystem by default. Is there any case we need to create ext4
> > with old 32 bytes block group descriptors?
>
> Because we will only have a single tool "mke2fs", and it should be able
> to format filesystems for all kernels.
I agree. I was wondering why not make the 64bytes block group descriptor
for ext4 as default. So by default we don't need to specify the size
when creating ext4 fs.
> Also, it may be desirable to
> make the descriptor larger for whatever reason (e.g. testing some new
> feature).
>
Okay, that could be useful for ext4. Don't feel ext2/3 needs that
option.
Regards,
Mingming
next prev parent reply other threads:[~2007-09-01 0:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 15:28 [PATCH 0/8][e2fsprogs] 64-bit block number support - first part Valerie Clement
2007-08-30 15:31 ` [PATCH 1/8][e2fsprogs] use existing function ext2fs_group_first_block() Valerie Clement
2007-10-14 22:53 ` Theodore Tso
2007-08-30 15:33 ` [PATCH 2/8][e2fsprogs] convert block number definition to blk_t Valerie Clement
2007-10-15 1:02 ` Theodore Tso
2007-08-30 15:37 ` [PATCH 3/8][e2fsprogs] add new -D <desc-size> option to mkfs Valerie Clement
2007-08-30 14:12 ` Andreas Dilger
2007-08-30 19:12 ` Mingming Cao
2007-08-30 20:51 ` Andreas Dilger
2007-09-01 0:25 ` Mingming Cao [this message]
2007-09-04 6:29 ` Andreas Dilger
2007-10-15 1:51 ` Theodore Tso
2007-08-30 15:38 ` [PATCH 4/8][e2fsprogs] add new macro to get descriptor number Valerie Clement
2007-10-15 2:09 ` Theodore Tso
2007-08-30 15:39 ` [PATCH 5/8][e2fsprogs] add new inline functions to get blocks counters Valerie Clement
2007-08-30 15:40 ` [PATCH 6/8][e2fsprogs] change access to the filesystem blocks counter Valerie Clement
2007-08-30 15:42 ` [PATCH 7/8][e2fsprogs] change access to the reserved " Valerie Clement
2007-08-30 15:43 ` [PATCH 8/8][e2fsprogs] change access to the free " Valerie Clement
2007-08-30 16:20 ` [PATCH 1/8][e2fsprogs] use existing function ext2fs_group_first_block() Valerie Clement
2007-10-14 15:12 ` [PATCH 0/8][e2fsprogs] 64-bit block number support - first part Theodore Tso
2007-10-17 14:13 ` Valerie Clement
2007-10-17 14:53 ` 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=1188606300.15123.9.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=valerie.clement@bull.net \
/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