From: tytso@valinux.com
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org,
Andreas Dilger <adilger@turbolinux.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Ext2 development mailing list <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] ext2 inode size (on-disk)
Date: Thu, 19 Apr 2001 16:10:03 -0400 [thread overview]
Message-ID: <20010419161003.E17837@snap.thunk.org> (raw)
In-Reply-To: <20001202014045.F2272@parcelfarce.linux.theplanet.co.uk> <Pine.GSO.4.21.0104190719240.16930-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0104190719240.16930-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Thu, Apr 19, 2001 at 07:55:20AM -0400
On Thu, Apr 19, 2001 at 07:55:20AM -0400, Alexander Viro wrote:
> Erm... Folks, can ->s_inode_size be not a power of 2? Both
> libext2fs and kernel break in that case.
This was a project that was never completed. I thought at one point
of allowing the inode size to be not a power of 2, but if you do that,
you really want to avoid letting an inode cross a block boundary ---
for reliability and performance reasons if nothing else.
It may simply be easiest at this point to require that the inode size
be a power of two, at least as far as going from 128 to 256 bytes,
just for compatibility reasons. (Although if we do that, the folks
who want to use extra space in the inode will come pooring out of the
woodwork, and we're going to have to careful to control who uses what
parts of the extended inode.)
In the long run, it probably makes sense to adjust the algorithms to
allow for non-power-of-two inode sizes, but require an incompatible
filesystem feature flag (so that older kernels and filesystem
utilities won't choke when mounting filesystems with non-standard
sized inodes.
- Ted
next prev parent reply other threads:[~2001-04-19 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001202014045.F2272@parcelfarce.linux.theplanet.co.uk>
2001-04-19 11:55 ` ext2 inode size (on-disk) Alexander Viro
2001-04-19 17:41 ` Andreas Dilger
2001-04-19 18:02 ` Alexander Viro
2001-04-19 19:24 ` Andreas Dilger
2001-04-20 2:12 ` Alexander Viro
2001-04-19 20:10 ` tytso [this message]
2001-04-19 20:29 ` [Ext2-devel] " Jeff Garzik
2001-04-20 6:30 ` Theodore Tso
2001-04-20 2:23 ` Alexander Viro
2001-04-20 5:35 ` Andreas Dilger
2001-04-20 6:37 ` Theodore Tso
2001-04-20 6:35 ` 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=20010419161003.E17837@snap.thunk.org \
--to=tytso@valinux.com \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@math.psu.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