All of lore.kernel.org
 help / color / mirror / Atom feed
From: cyjoyp <cyjoyp@gmail.com>
To: xfs@oss.sgi.com
Subject: Inode Core, di_format = 3 , with sb_inodesize=1024
Date: Wed, 5 Nov 2008 21:38:25 -0800 (PST)	[thread overview]
Message-ID: <20355466.post@talk.nabble.com> (raw)


Hello folks,
    Referring to the document "XFS File System Structure" by Silicon
Graphics ,page number 34 ....
    "* On disk, the B+tree node starts with the xfs_bmbr_block_t header
followed by an array of 
        xfs_bmbt_key_t  values and then an array of xfs_bmbt_ptr_t
values.The size of 
        both arrays is specified by the header's bb_numrecs value ."
   "* The root node in the inode can only contain up to 19 key/pointer pairs
for a standard 256 byte inode 
       before a new level of nodes is added between the root and the
leaves."

My query is,
      
       I do not see the header  xfs_bmbr_block_t anywhere else in the
documentation.Is it a 
       spelling a mistake? As far as I understand, bb_numrecs represents the
number of pointers present in 
       the Inode core and not the size of the key/pointer arrays.This
pointer value helps us reach the 
       block of extents having the signature BMAP. Please correct me if I am
wrong.

       If there are up to 19 key/pointer pairs for a standard 256 byte
Inode, do any one know how 
       may key/pointer pair does a Inode core of size 512 and 1024 will
have????
       Is there any way to calculate the offset of the pointer ??

  Pleas help me
       

      



-- 
View this message in context: http://www.nabble.com/Inode-Core%2C-di_format-%3D-3-%2C-with-sb_inodesize%3D1024-tp20355466p20355466.html
Sent from the Xfs - General mailing list archive at Nabble.com.

                 reply	other threads:[~2008-11-06  5:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20355466.post@talk.nabble.com \
    --to=cyjoyp@gmail.com \
    --cc=xfs@oss.sgi.com \
    /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.