public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: coly <colyli@gmail.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: confused on different inode size
Date: Sun, 08 Apr 2007 14:39:03 +0800	[thread overview]
Message-ID: <1176014343.20429.6.camel@colyT43.site> (raw)

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.

I believe there is something I missed, can anybody give me some points ?

Thanks in advance.

Coly

             reply	other threads:[~2007-04-08  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08  6:39 coly [this message]
2007-04-08 17:52 ` confused on different inode size Theodore Tso
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=1176014343.20429.6.camel@colyT43.site \
    --to=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