xfs
[Top] [All Lists]

Re: Find file for inode

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Find file for inode
From: Nathan Scott <nathans@xxxxxxx>
Date: Tue, 23 Aug 2005 07:24:41 +1000
In-reply-to: <20050822124508.GC29623@butterblume>; from mm@xxxxxxxxxxxxxxx on Mon, Aug 22, 2005 at 02:45:08PM +0200
References: <20050820093341.GA15491@butterblume> <20050821224849.GB845@frodo> <20050822124508.GC29623@butterblume>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Mon, Aug 22, 2005 at 02:45:08PM +0200, Markus Meyer wrote:
> On [Mon, Aug 22 08:48], Nathan Scott wrote:
> >xfs_db> blockfree
> >xfs_db> blockget -n
> 
> Thx at first.
> From this point on the thing ran for nearly two hours so I quit it. This

This probably depends on filesystem size and number of inodes,
for my test case on a relatively small filesystem it finished
immediately.

I guess, since your looking into this, you may also have bad
blocks being remapped underneath the filesystem... and its
possible thats increasing your run time too.

> interface is cryptic and the documentation is written in Geekish :)

Erm, any interfaces or docs in particular you didn't understand?

> ASAP I'll switch back to EXT3. 

OK, whatever makes your boat float.

> >Oh, and initially you'll need to get from disk address (512 bytes) to
> >a filesystem block number - use the convert command:
> >
> >xfs_db> convert fsb 98319 daddr
> >0x19020 (102432)
> >xfs_db> convert daddr 102432 fsb
> >0x1800f (98319)
> 
> OK, this I just can't wrap my head around. Sorry.

Its described further in the xfs_db(8) man page.

cheers.

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>