From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: [PATCH] debugfs: document zap_block & dump_block
Date: Fri, 11 Jan 2013 11:40:25 -0600 [thread overview]
Message-ID: <50F04E89.7070501@redhat.com> (raw)
What little docs there were had a cut & paste error.
We can do better. :)
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/debugfs/debug_cmds.ct b/debugfs/debug_cmds.ct
index 520933a..9a05ef7 100644
--- a/debugfs/debug_cmds.ct
+++ b/debugfs/debug_cmds.ct
@@ -181,10 +181,10 @@ request do_set_mmp_value, "Set MMP value",
request do_extent_open, "Open inode for extent manipulation",
extent_open, eo;
-request do_zap_block, "Zap block",
+request do_zap_block, "Zap block: fill with 0, pattern, flip bits etc.",
zap_block, zap;
-request do_dump_block, "Zap block",
+request do_dump_block, "Dump contents of a block",
block_dump, bp;
end;
diff --git a/debugfs/debugfs.8.in b/debugfs/debugfs.8.in
index bfcb1a8..4164c3a 100644
--- a/debugfs/debugfs.8.in
+++ b/debugfs/debugfs.8.in
@@ -215,6 +215,10 @@ option is given set the owner, group and permissions information on
to match
.IR filespec .
.TP
+.I dump_block [-f out_file] block_num
+Dump the contents of a block, optionally to
+.IR out_file .
+.TP
.I dump_mmp
Display the multiple-mount protection (mmp) field values.
.TP
@@ -612,6 +616,14 @@ Create a file in the filesystem named
and copy the contents of
.I source_file
into the destination file.
+.TP
+.I zap_block [-f file] [-o offset] [-l length] [-p pattern] block_num
+Zero, or pattern-fill, portions of a block within a file or
+within the filesystem.
+.TP
+.I zap_block [-f file] [-b bit] block_num
+Bit-flip portions of a block within a file or
+within the filesystem.
.SH ENVIRONMENT VARIABLES
.TP
.B DEBUGFS_PAGER, PAGER
next reply other threads:[~2013-01-11 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 17:40 Eric Sandeen [this message]
2013-01-12 22:22 ` debugfs: document zap_block & dump_block Theodore Ts'o
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=50F04E89.7070501@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.