linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Matthew Friday <lkmfriday@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Do btrfs provide filesystem debugger?
Date: Wed, 23 Jan 2019 07:46:23 +0800	[thread overview]
Message-ID: <94fb82b7-1395-7fad-5d95-87a9d96927f8@gmx.com> (raw)
In-Reply-To: <CANmnzbMpBsE5dcmc9_mHOTB9tUY7enWxicRCbmTwpZ2HuDOhaw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 874 bytes --]



On 2019/1/23 上午7:41, Matthew Friday wrote:
> Hi all,
> 
> I recently started learning BTRFS internals, and one think that I
> cannot find is filesystem debugger to browse on disk data structures
> (like xfs_db or ext debugfs).

You need "btrfs inspect dump-tree" and "btrfs inspect dump-super"

> Do BTRFS provide similar way to navigate on disk structures? I can see
> the btrfs-debug-tree utility which provide whole tree of the
> informations, is this something that can be then perhaps parsed in
> easy way to view the internal structures?

It's already all the internal structures.

Unlike other fs, btrfs uses a generic way to organize all its info, as
btrfs btree.

So dump tree provides everything you need, from inode and dentry info to
all internal data like allocation and csum data.

Thanks,
Qu

> 
> Many Thanks
> Matt
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-01-22 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 23:41 Do btrfs provide filesystem debugger? Matthew Friday
2019-01-22 23:46 ` Qu Wenruo [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=94fb82b7-1395-7fad-5d95-87a9d96927f8@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkmfriday@gmail.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;
as well as URLs for NNTP newsgroup(s).