public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>,
	xfs@oss.sgi.com
Subject: Re: Recovery of deleted files/directories
Date: Thu, 07 Aug 2014 09:45:43 -0500	[thread overview]
Message-ID: <53E39117.4090200@sandeen.net> (raw)
In-Reply-To: <CACyNnZNAZUSf1Veybw24hU0snaTyp+Yg+wXS1_Kv-rynQjzjuw@mail.gmail.com>

On 8/7/14, 8:41 AM, Felipe Monteiro de Carvalho wrote:
> On Thu, Aug 7, 2014 at 2:56 PM, Brian Foster <bfoster@redhat.com> wrote:
>>> But di_mode in particular is a key element as I am using it to
>>> differentiate files from directories.
>> In general you can't rely on on-disk data once the inode has been freed.
>> Perhaps you should start a new thread with some kind of write up about
>> what you're trying to accomplish and how you're going about it.
> 
> Yes, I know it is unreliable, and that's OK for me. I'm satisfied in
> having a best effort solution which works often, it does not have to
> be fully reliable.
> 
> What I am trying to accomplish is quite simple: Recover as many
> deleted files in a XFS partition as possible. For example if someone
> deletes a file by mistake, how to get it back?

Do you have a link to the project you're working on?  Is it an open
source tool?

There's another tool out there already called "xfs_irecover" which
looks for any inode anywhere on disk, and tries to copy back out any
data that it points to, deleted or not.  It could use some love.

Thanks,
-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-08-07 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 13:41 Recovery of deleted files/directories Felipe Monteiro de Carvalho
2014-08-07 14:45 ` Eric Sandeen [this message]
2014-08-08  8:54   ` Felipe Monteiro de Carvalho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53E39117.4090200@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=felipemonteiro.carvalho@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox