From: Jeff Liu <jeff.liu@oracle.com>
To: xfs@oss.sgi.com
Subject: XFS AG disk layout described on official doc is wrong
Date: Fri, 09 Nov 2012 14:47:41 +0800 [thread overview]
Message-ID: <509CA70D.6000702@oracle.com> (raw)
Hello,
I observed that there is an issue on our official DOC for AG disk
layout, which can be found at:
http://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/Allocation_Groups.html
It shows that the IBT block is followed by the block where AGFL sector
resides. However, it should be followed by the
CNT block according to my debug, like below:
-------------------------------
superblock
AG free block info
AG inode B+tree info
AG internal free list
-------------------------------
Root of free space B+tree
B+tree key is block number
-------------------------------
Root of free space B+tree
B+tree key is block count
--------------------------------
Root of inodes B+tree
--------------------------------
Maybe the DOC is old, or am I missing anything? If not, can we correct it?
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-11-09 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 6:47 Jeff Liu [this message]
2012-11-09 7:36 ` XFS AG disk layout described on official doc is wrong Dave Chinner
2012-11-09 7:45 ` Jeff Liu
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=509CA70D.6000702@oracle.com \
--to=jeff.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox