| To: | Michal Soltys <nozo@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Map a disk LBA to filename? |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 28 Oct 2008 10:35:16 +1100 |
| Cc: | Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4905BC13.3030402@drutsystem.com> |
| Mail-followup-to: | Michal Soltys <nozo@xxxxxxxxxxxxxx>, Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <4905A3FB.6080709@aei.mpg.de> <20081027114945.GE4985@disturbed> <4905B48A.8010108@aei.mpg.de> <4905BC13.3030402@drutsystem.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Mon, Oct 27, 2008 at 02:03:15PM +0100, Michal Soltys wrote: > Carsten Aulbert wrote: >> >> Dave Chinner wrote: >>> Use xfs_bmap to find the location on disk of the extents in each >>> file. Recurse over the filesystem until you find the file that owns >>> the block that went bad. >> >> Sounds like a tedious but doable route to take. >> > > Wouldn't something like (under xfs_db) : > > getblock -b #block -n > ncheck -i #inode > > where required #inode is reported by getblock > > do the thing ? Blockget - yes it will. It just does the traversal internally to build the mapping. With large filesystems xfs_db can run out of memory building the mapping, which is why I've used the explicit traverse+xfs_bmap method in the past.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Bad day with xfsrestore, what went wrong?, Bill Kendall |
|---|---|
| Next by Date: | Re: [PATCH 1/2] wire up ->open for directories, Dave Chinner |
| Previous by Thread: | Re: Map a disk LBA to filename?, Michal Soltys |
| Next by Thread: | Re: Map a disk LBA to filename?, Carsten Aulbert |
| Indexes: | [Date] [Thread] [Top] [All Lists] |