| To: | Pradeep Kumar <praks411@xxxxxxxxx> |
|---|---|
| Subject: | Re: 128 bits extent bmap for file format 2 |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 22 Oct 2013 11:12:18 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAPU9cc3rV+E79HBE95=nsjgoC5=s85jBBZgcxL+d8KijVa0LyA@xxxxxxxxxxxxxx> |
| References: | <CAPU9cc3rV+E79HBE95=nsjgoC5=s85jBBZgcxL+d8KijVa0LyA@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: fix possible NULL dereference, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH] xfs: fix possible NULL dereference, Dave Chinner |
| Previous by Thread: | 128 bits extent bmap for file format 2, Pradeep Kumar |
| Next by Thread: | Re: 128 bits extent bmap for file format 2, Pradeep Kumar |
| Indexes: | [Date] [Thread] [Top] [All Lists] |