| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Find file for inode |
| From: | Markus Meyer <mm@xxxxxxxxxxxxxxx> |
| Date: | Mon, 22 Aug 2005 14:45:08 +0200 |
| In-reply-to: | <20050821224849.GB845@frodo> |
| Mail-followup-to: | linux-xfs@xxxxxxxxxxx |
| References: | <20050820093341.GA15491@butterblume> <20050821224849.GB845@frodo> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | mutt-ng/devel (Linux) |
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 is nothing near a usable "solution". That's not against you. XFS is nice as long as it works. But then it gets really complicated. The programs interface is cryptic and the documentation is written in Geekish :) ASAP I'll switch back to EXT3. Oh, and initially you'll need to get from disk address (512 bytes) to a filesystem block number - use the convert command:
Cheers, -- Markus Meyer - encrypted email preferred -> GPG: B87120ED
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | URG; need your support. plz, 이금석 |
|---|---|
| Next by Date: | XFS for ARM, Lan . Chen |
| Previous by Thread: | Re: Find file for inode, Nathan Scott |
| Next by Thread: | Re: Find file for inode, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |