From: liubo <liubo2009@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Backref walking utilities
Date: Mon, 23 May 2011 05:53:43 -0400 [thread overview]
Message-ID: <4DDA2EA7.9080305@cn.fujitsu.com> (raw)
Hi,
As one of my plans, I'm going to take this project over unless someone has been working on it.
>From wiki, quote:
Backref walking utilities
Given a block number on a disk, the Btrfs metadata can find all the files and directories
that use or care about that block. Some utilities to walk these back refs and print the
results would help debug corruptions.
Given an inode, the Btrfs metadata can find all the directories that point to the inode.
We should have utils to walk these back refs as well.
end quote.
And I have some thoughts to share with you:
- Clearly, this is going to be another command. Just like the command "btrfs-debug-tree",
btrfs-walk-backref also needs to be able to track btrfs's metadata in
a) the offline situation (at a umount state), or
b) the corrupted situation.
- For block number, the main goal is to find relative extent backrefs. When it comes to
those shared blocks, maybe things will be more complex.
- For inode, the main goal is to find relative inode refs. And we should be cautious about
a) an inode with hard links, b) snapshot.
Did I miss or misunderstand something? Any comments are welcomed. :)
thanks,
liubo
next reply other threads:[~2011-05-23 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:53 liubo [this message]
2011-05-23 10:02 ` Backref walking utilities Arne Jansen
2011-05-23 10:15 ` Hugo Mills
2011-05-25 15:08 ` Jan Schmidt
2011-05-26 1:51 ` liubo
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=4DDA2EA7.9080305@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).