From: Theodore Tso <tytso@mit.edu>
To: coly <colyli@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: confused on different inode size
Date: Sun, 8 Apr 2007 13:52:18 -0400 [thread overview]
Message-ID: <20070408175218.GB29180@thunk.org> (raw)
In-Reply-To: <1176014343.20429.6.camel@colyT43.site>
On Sun, Apr 08, 2007 at 02:39:03PM +0800, coly wrote:
> Hi, list:
>
> I find size of struct ext4_inode is 152 bytes, but from the dumpe2fs, it
> tells me the inode size is 128 bytes.
>
> I am confused that, the ext4_inode is the on-disk inode format, so how
> can dumpe2fs tells the inode size is 128 bytes.
>
> Further more, when I use sb_bread() to read inode from inode table (with
> 152 bytes inode size), I can not read proper data from the bh->b_data.
> Once I use 128 bytes inode size, I can read what I want from the
> bh->b_data.
The inode size for ext4 filesystems can be multiple sizes; the
traditional ext2/ext3 inode size is 128 bytes. If so, then you won't
have any of the features that require inode fields starting at
i_extra_isize. If you use an inode size of 256 bytes, then you will
be able to use nanosecond granularity timestamps, and the extra space
(256-152 bytes) can be used for fast access to extended attributes.
If there is an expectation that the filesystem will need a larger
amount of space for extended attributes, the filesystem can be
formatted with 512, 1024, or even larger sizes (so long as it is a
power of two >= 128 bytes).
- Ted
next prev parent reply other threads:[~2007-04-08 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 6:39 confused on different inode size coly
2007-04-08 17:52 ` Theodore Tso [this message]
2007-04-09 2:33 ` coly
2007-04-09 15:26 ` Theodore Tso
2007-04-09 15:58 ` coly
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=20070408175218.GB29180@thunk.org \
--to=tytso@mit.edu \
--cc=colyli@gmail.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