From: Divya Indi <divya.indi@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: ashish.samant@oracle.com, bo.li.liu@oracle.com
Subject: [PATCH 2/3] btrfs-progs: Add a command to show bg info
Date: Mon, 17 Oct 2016 17:35:14 -0700 [thread overview]
Message-ID: <1476750915-3105-3-git-send-email-divya.indi@oracle.com> (raw)
In-Reply-To: <1476750915-3105-2-git-send-email-divya.indi@oracle.com>
Add a new subcommand to btrfs inspect-internal
btrfs inspect-internal bg_analysis <path>
Gives information about all the block groups.
Signed-off-by: Divya Indi <divya.indi@oracle.com>
Reviewed-by: Ashish Samant <ashish.samant@oracle.com>
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
---
cmds-inspect.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 114 insertions(+), 0 deletions(-)
diff --git a/cmds-inspect.c b/cmds-inspect.c
index f435ea9..0e2f15a 100644
--- a/cmds-inspect.c
+++ b/cmds-inspect.c
@@ -147,6 +147,118 @@ static int get_bg_info(int fd, struct btrfs_ioctl_search_args *bg_args,
}
return ret;
}
+
+static const char * const cmd_inspect_bg_analysis_usage[] = {
+ "btrfs inspect-internal bg_analysis <path> ",
+ "Get information about all block groups",
+ "",
+ "",
+ NULL
+};
+
+static int cmd_inspect_bg_analysis(int argc, char **argv)
+{
+ struct btrfs_ioctl_search_args args;
+ struct btrfs_ioctl_search_args bg_args;
+ struct btrfs_ioctl_search_header *header;
+ struct btrfs_ioctl_search_header *bg_header;
+ struct btrfs_ioctl_search_key *sk;
+ struct btrfs_ioctl_search_key *bg_sk;
+ struct btrfs_block_group_item *bg;
+ struct btrfs_chunk *chunk;
+ unsigned long off = 0;
+ unsigned long bg_off = 0;
+ DIR *dirstream = NULL;
+ int fd;
+ int i;
+ int ret = 0;
+ u64 used;
+ u64 flags;
+ char bg_type[32] = {0};
+
+ if (check_argc_exact(argc, 2))
+ usage(cmd_inspect_bg_analysis_usage);
+
+ fd = btrfs_open_dir(argv[optind], &dirstream, 1);
+ if (fd < 0)
+ return 1;
+
+ memset(&args, 0, sizeof(args));
+ sk = &args.key;
+ sk->min_offset = sk->min_transid = 0;
+ sk->max_offset = sk->max_transid = (u64)-1;
+ printf("%20s%20s%20s%20s\n", "Type", "Start", "Len", "Used");
+ while (1) {
+
+ /* Walk through the chunk tree and retrieve all the chunks */
+ ret = get_chunks(fd, &args);
+ if (ret < 0)
+ goto out;
+
+ /*
+ * it should not happen.
+ */
+ if (sk->nr_items == 0)
+ break;
+
+ off = 0;
+ memset(&bg_args, 0, sizeof(bg_args));
+ bg_sk = &bg_args.key;
+
+ bg_sk->tree_id = BTRFS_EXTENT_TREE_OBJECTID;
+ bg_sk->min_type = BTRFS_BLOCK_GROUP_ITEM_KEY;
+ bg_sk->max_type = BTRFS_BLOCK_GROUP_ITEM_KEY;
+ bg_sk->min_transid = 0;
+ bg_sk->max_transid = (u64)-1;
+
+ for (i = 0; i < sk->nr_items; i++) {
+ header = (struct btrfs_ioctl_search_header *)(args.buf
+ + off);
+ off += sizeof(*header);
+ if (header->type == BTRFS_CHUNK_ITEM_KEY) {
+ chunk = (struct btrfs_chunk *)
+ (args.buf + off);
+
+ /* For every chunk lookup an exact match(bg) in
+ * the extent tree and read its used values */
+ ret = get_bg_info(fd, &bg_args, header->offset,
+ chunk->length);
+ if (ret < 0)
+ goto out;
+
+ /*
+ * it should not happen.
+ */
+ if (bg_sk->nr_items == 0)
+ continue;
+
+ bg_off = 0;
+ bg_header = (struct btrfs_ioctl_search_header *)
+ (bg_args.buf + bg_off);
+ bg_off += sizeof(*bg_header);
+ bg = (struct btrfs_block_group_item *)
+ (bg_args.buf + bg_off);
+
+ used = btrfs_block_group_used(bg);
+ memset(&bg_type, 0, 32);
+ flags = btrfs_block_group_flags(bg);
+ bg_flags_to_str(flags, bg_type);
+ printf("%20s%20llu%20s%20s\n",
+ bg_type,
+ bg_header->objectid,
+ pretty_size(bg_header->offset),
+ pretty_size(used));
+ }
+ off += header->len;
+ sk->min_offset = header->offset + header->len;
+ }
+ sk->nr_items = 4096;
+ }
+out:
+ close_file_or_dir(fd, dirstream);
+ return ret;
+}
+
static const char * const cmd_inspect_inode_resolve_usage[] = {
"btrfs inspect-internal inode-resolve [-v] <inode> <path>",
"Get file system paths for the given inode",
@@ -702,6 +814,8 @@ const struct cmd_group inspect_cmd_group = {
0 },
{ "min-dev-size", cmd_inspect_min_dev_size,
cmd_inspect_min_dev_size_usage, NULL, 0 },
+ { "bg_analysis", cmd_inspect_bg_analysis,
+ cmd_inspect_bg_analysis_usage, NULL, 0 },
{ "dump-tree", cmd_inspect_dump_tree,
cmd_inspect_dump_tree_usage, NULL, 0 },
{ "dump-super", cmd_inspect_dump_super,
--
1.7.1
next prev parent reply other threads:[~2016-10-18 0:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 0:35 btrfs-progs: Add 2 new subcommands to inspect-internal Divya Indi
2016-10-18 0:35 ` [PATCH 1/3] btrfs-progs: Generic functions to retrieve chunks and their bg info Divya Indi
2016-10-18 0:35 ` Divya Indi [this message]
2016-10-18 0:35 ` [PATCH 3/3] btrfs-progs: Add command to check if balance op is req Divya Indi
2016-10-18 1:42 ` Qu Wenruo
2016-10-19 17:08 ` Divya Indi
2016-10-28 15:20 ` David Sterba
2016-10-28 16:29 ` Graham Cobb
2016-10-31 16:33 ` David Sterba
2016-11-02 0:39 ` divya.indi
2016-10-30 14:10 ` Qu Wenruo
2016-10-18 1:39 ` [PATCH 2/3] btrfs-progs: Add a command to show bg info Qu Wenruo
2016-10-18 5:24 ` Roman Mamedov
2016-10-19 17:33 ` Divya Indi
2016-10-28 16:00 ` David Sterba
2016-11-02 0:40 ` divya.indi
2016-10-18 1:34 ` [PATCH 1/3] btrfs-progs: Generic functions to retrieve chunks and their " Qu Wenruo
2016-10-28 15:44 ` David Sterba
2016-11-02 0:39 ` divya.indi
2017-06-07 17:03 ` Goffredo Baroncelli
2017-06-09 21:57 ` divya.indi
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=1476750915-3105-3-git-send-email-divya.indi@oracle.com \
--to=divya.indi@oracle.com \
--cc=ashish.samant@oracle.com \
--cc=bo.li.liu@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).