| To: | Andi Kleen <andi@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Fwd: Need assistance on XFS undeleting files |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 06 Jul 2010 14:44:28 -0500 |
| Cc: | James Shih <shija03@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <87fwzwx0rr.fsf@xxxxxxxxxxxxxxxxx> |
| References: | <AANLkTik59zx97OVNXSfk4Gbe5poVAIGgJiTJVlsJZIjL@xxxxxxxxxxxxxx> <201007060807.24582.misiek@xxxxxxxxxx> <AANLkTikhinYuUDsT-5hqyNkR89Y4PeosvAQ3K2LFqYkn@xxxxxxxxxxxxxx> <87fwzwx0rr.fsf@xxxxxxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.24 (Macintosh/20100228) |
Andi Kleen wrote: > James Shih <shija03@xxxxxxxxx> writes: >> I would like to know if the development team carries such tools - >> tools that allow one to list the inodes of the XFS filesystem of >> deleted files, and tools that allow one to cat (dump) the blocks from >> a starting inode to all the following blocks until an indication that >> the file is ended or a new indication of a new file appears. (these >> tools would correspond to TCT's ils and pcat respectively). > > XFS has no separate reserved inode table (but just allocates/free blocks > in the fs), so it can be difficult to even find the inodes when they're > gone. However, xfs_irecover (http://jengelh.medozas.de/projects/hxtools/) may help, as long as the fs hasn't been written to much post-delete of course. -Eric > -Andi > |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO), Stan Hoeppner |
|---|---|
| Next by Date: | Re: Re: CentOS 5.5 XFS internal errors (XFS_WANT_CORRUPTED_GOTO), Shaun Adolphson |
| Previous by Thread: | Re: Fwd: Need assistance on XFS undeleting files, Andi Kleen |
| Next by Thread: | Responsible employees are needed. Job ID 1278508589, Pandora Mclean |
| Indexes: | [Date] [Thread] [Top] [All Lists] |