From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: chris.mason@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: [RFC PATCH] Add debug-btrfs command to btrfs-progs
Date: Sun, 31 Jan 2010 19:51:34 +0530 [thread overview]
Message-ID: <1264947698-32371-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
Hi,
The below set of patches add debug-btrfs command to btrfs-progs package.
The new command depends on the libss.a library provided e2fsprogs. To build
one have to set E2FSPRGS_BUILD_DIR to point to the e2fsprogs build directory.
Once we get e2fsprogs to create a proper libss package we should be able
to remove the above export.
Currently supported list of commands are listed below. It should be really
easy to add new commands
debug-btrfs: ?
Available debug-btrfs requests:
show_debugfs_params, params
Show btrfs_debug parameters
open_filesys, open Open the file system
dump_tree Show full btrfs tree
dump_root_tree Show root tree
dump_chunk_tree Show btrfs chunk tree
print_inode Print inode details
help Display info on command or topic.
list_requests, lr, ? List available commands.
quit, q Leave the subsystem.
You should be able to get the patches with --no-renames at
http://www.kernel.org/pub/linux/kernel/people/kvaneesh/debug-btrfs/
-aneesh
next reply other threads:[~2010-01-31 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 14:21 Aneesh Kumar K.V [this message]
2010-01-31 14:21 ` [PATCH 1/4] btrfs-progs: Move files around Aneesh Kumar K.V
2010-01-31 14:21 ` [PATCH 2/4] btrfs-progs: Add debug-btrfs command Aneesh Kumar K.V
2010-01-31 14:21 ` [PATCH 3/4] debug-btrfs: Add open file system command Aneesh Kumar K.V
2010-01-31 14:21 ` [PATCH 4/4] debug-btrfs: Add print_inode command Aneesh Kumar K.V
2010-02-01 4:36 ` [PATCH 5/6] debug-btrfs: Add command to dump each of the btrfs trees Aneesh Kumar K.V
2010-02-01 4:36 ` [PATCH 6/6] debug-btrfs: Add pager support Aneesh Kumar K.V
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=1264947698-32371-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.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