128 bits extent bmap for file format 2

[Pradeep Kumar]

Hi Dave,

Thanks for the reply. I think I may get my solution. Can you explain the
difference between the two?
I've created sample xfs file using mkfs.xfs with mostly default parameter
1. Sector Size = 512
2. Block size = 4096
3. AG Number = 2
4. Number of blocks per AG = 6400.

So when I get absolute block 9420 from file extent data  I'm going to (6400
+ 3020) , 3020 block of second AG which is wrong. The file start from 7628
absolute block or (6400 + 1228), 1228 block of second AG.
Please describe in some detail above the conversion which you are talking
about.

Thanks and Regards,
Pradeep



On 22 October 2013 02:12, Dave Chinner <david at fromorbit.com> wrote:

> On Tue, Oct 22, 2013 at 01:32:22AM +0200, Pradeep Kumar 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).
>
> Extents use filesystem block encodings, not disk addresses. Look up
> the macros XFS_DADDR_TO_FSB and XFS_FSB_TO_DADDR.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david at fromorbit.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20131022/710a9544/attachment.html>