From: Greg Freemyer <greg.freemyer@gmail.com>
To: Pradeep Kumar <praks411@gmail.com>, xfs@oss.sgi.com
Subject: Re: 128 bits extent bmap for file format 2
Date: Tue, 22 Oct 2013 09:11:06 -0400 [thread overview]
Message-ID: <a3208864-e046-4034-ac3b-1ce6f7ae352b@email.android.com> (raw)
In-Reply-To: <CAPU9cc3rV+E79HBE95=nsjgoC5=s85jBBZgcxL+d8KijVa0LyA@mail.gmail.com>
Pradeep Kumar <praks411@gmail.com> wrote:
>Hi,
>
>I'm writing a small utility to parse XFS fs image on windows.
>I'm able to fetch the files in the first AG (0).
>However when it comes to the files which are in different AG I'm facing
>some problem in parsing extent bmap 128bits data of file inode (format
>==
>2).
>
>Here is the sample 128bits data
>1. 00 00 00 00 00 00 00 00 00 00 00 04 99 80 00 01 (LSB)
>
>After unpacking the bits are per doc and source code
>In the above case I'm getting following
>Num Of blocks = 1 (correct) (0 to 20 bits)
>absolute block number = 9420 (0x24CC) (wrong) (21 to 72)
>file offset = 0 (72 to 126)
>
>I'm always getting wrong absolute block number . Actual data is in
>block
>7628 (0x1DCC).
>No matter what I try I'm always getting the same result. I've even
>verified
>this
>by using the code from xfs_bmbt_get_all function from xfs source which
>too
>gives me same result (9420).
>Please someone help me with this. I'm stuck on this from 3 days.
>
>Thanks and Regards,
>Pradeep
Pradeep,
It would be cool if your utility could be incorporated into sleuthkit. Sleuthkit has fat and NTFS parsers for sure already. I think ext2 and ext3. Adding a xfs parser would be a cool addition.
http://www.sleuthkit.org/sleuthkit/docs/api-docs/index.html#users_guide
Fyi: sleuthkit has been around for a long time, but it is still actively maintained and heavily used. It is in several linux distros, but is also available for windows.
Greg
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-22 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 23:32 128 bits extent bmap for file format 2 Pradeep Kumar
2013-10-22 0:12 ` Dave Chinner
2013-10-22 8:08 ` Pradeep Kumar
2013-10-22 11:25 ` Pradeep Kumar
2013-10-22 15:03 ` Eric Sandeen
2013-10-22 13:11 ` Greg Freemyer [this message]
2013-11-03 5:20 ` Pradeep Kumar
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=a3208864-e046-4034-ac3b-1ce6f7ae352b@email.android.com \
--to=greg.freemyer@gmail.com \
--cc=praks411@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox