From: "Michael Li (gmail)" <mikore.li@gmail.com>
To: nathans@sgi.com, xfs@oss.sgi.com
Subject: XFS bmap to disk lba question.
Date: Fri, 14 Jul 2006 01:58:04 +0800 [thread overview]
Message-ID: <44B689AC.8030408@gmail.com> (raw)
Hi, Nathans and all,
I am looking for the way to map bmap of file extent to disk physical LBA
on IRIX/CXFS. Since here is the BEST place to get help about XFS, I send
my confusion to you.
We know that the command xfs_bmap can show us the file's extent range,
for example [20 - 100], but how can we know the real physical secoter ID
(or
named as LBA) of file's first block(512Bytes) on a raw disk? I've read
XVM admin for IRIX, it show us less clue for this mapping.
We can get this mapping method on linux, as linux/xfs is open sourced,
but IRIX is not, we don't know how to do it on IRIX, although the
filesystem is the in the same name XFS.
Furthermore, is it the same way to mapping the bmap/LBA in a striped
volume. For example: a file on striped volume is in bmap range[20, 1000].
there are 3 physical disks(disk1/disk2/disk3) in the stripe, stripe
unit is 128. each stripe unit has 32 512B-blocks. How can we map the
first block in the file to one of disk's X sector?
After read XVM document. the stripe chunksize should be 128*32 blocks,
the stripe width is 3. In the special case, the file's first block must
belong to disk1.
But how can we know the real LBA on disk1? assume it is a very simple
stripe group, not for log subvolume/realtime subvolume.
Could you help me?
Thanks very much!
Michael
BTW: If we should not talk about IRIX here, I will stop posting such a
topic here. Sorry for the noise.
next reply other threads:[~2006-07-13 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 17:58 Michael Li (gmail) [this message]
2006-07-14 5:31 ` XFS bmap to disk lba question Nathan Scott
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 5:52 Sebastian Brings
2006-07-14 13:42 ` Michael Li (gmail)
2006-07-14 9:46 Michael Li (Gmail)
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=44B689AC.8030408@gmail.com \
--to=mikore.li@gmail.com \
--cc=nathans@sgi.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