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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
