From: Carlos Maiolino <cmaiolino@redhat.com>
To: "Chang, Brady" <Brady.Chang@emc.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs_irecover question
Date: Mon, 27 Jun 2016 11:46:19 +0200 [thread overview]
Message-ID: <20160627094619.GB29774@redhat.com> (raw)
In-Reply-To: <D392E1CC.3E982%brady.chang@emc.com>
On Fri, Jun 24, 2016 at 06:10:38PM +0000, Chang, Brady wrote:
> Hi,
>
> Is there a way to find fullpath to the file generated by xfs_irecover
> ?
I'm not a user of xfs_irecover, but, giving how inodes are deleted, I doubt you
will be able to recover the fullpath in some way. While we don't delete inodes
from the lists and make them usable for future files, this is not the same for
directory entries. The directory entry is removed from the directory, and there
is nothing that can link the inode to its directory entry (or entries) after the
file is deleted. Somebody with more expertise on it might give a final POV, but
I doubt you would be able to recover the directory entries pointing to the
inode, once the file is deleted.
>
> For example:
> [root@sdw2 recover]# ls -l 532946
> -rw------- 1 root root 33461216 Jun 23 21:07 532946
> [root@sdw2 recover]# file 532946
> 532946: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
>
> Thanks
>
> -Brady
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-06-27 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 18:10 xfs_irecover question Chang, Brady
2016-06-27 9:46 ` Carlos Maiolino [this message]
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=20160627094619.GB29774@redhat.com \
--to=cmaiolino@redhat.com \
--cc=Brady.Chang@emc.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