From: "Theodore Ts'o" <tytso@mit.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: Andreas Dilger <adilger@clusterfs.com>,
sho@tnes.nec.co.jp, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] [PATCH] ext3: Extends blocksize up to pagesize
Date: Sun, 22 Jan 2006 13:31:28 -0500 [thread overview]
Message-ID: <20060122183128.GB7082@thunk.org> (raw)
In-Reply-To: <20060120231016.40b40fd7.akpm@osdl.org>
On Fri, Jan 20, 2006 at 11:10:16PM -0800, Andrew Morton wrote:
> Andreas Dilger <adilger@clusterfs.com> wrote:
> > Just for others' info - the fill_super change has been tested in the past
> > by Sonny Rao at IBM also. e2fsprogs has supported this for a long time
> > already.
>
> I have a vague memory that there's some piece of metadata (per-block-group
> info, I think) which will overflow at 8kb blocksize. I say this in the
> hope that you'll remmeber what it was ;)
The limiting factor is bg_free_blocks_count (and to some extent,
possibly bg_free_inodes_dir), which is a 16 bit field. At 8kb, the
default block group size is 8kb * 8 bits/byte == 65536. At 16kb, a
block group size of 131072 would overflow bg_free_blocks_count. You
could of course artificially limit the block group size to 65536 for
block sizes > 16kb. The better thing to do would be to use the extra
space in the per-block group metadata to extend those fields to 32
bits.
- Ted
next prev parent reply other threads:[~2006-01-22 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:06 [PATCH] ext3: Extends blocksize up to pagesize Takashi Sato
2006-01-18 15:48 ` John Stoffel
2006-01-22 18:28 ` Theodore Ts'o
2006-01-23 5:43 ` [Ext2-devel] " Andreas Dilger
2006-01-23 20:36 ` Folkert van Heusden
2006-01-23 8:30 ` Helge Hafting
2006-01-18 18:52 ` [Ext2-devel] " Andreas Dilger
2006-01-21 7:10 ` Andrew Morton
2006-01-22 18:31 ` Theodore Ts'o [this message]
2006-01-23 5:38 ` 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=20060122183128.GB7082@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
/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.