From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: [PATCH] debugfs: document htree-related commands in man page
Date: Wed, 11 May 2011 11:49:07 -0500 [thread overview]
Message-ID: <4DCABE03.7040300@redhat.com> (raw)
The debugfs commands dirsearch, dx_hash, and htree_dump were
never documented in the man page. Do so.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
Please feel free to check my manpage-fu, as well as checking
for accurate descriptions of these commands, thanks...
diff --git a/debugfs/debugfs.8.in b/debugfs/debugfs.8.in
index 41c73fd..f5deb7a 100644
--- a/debugfs/debugfs.8.in
+++ b/debugfs/debugfs.8.in
@@ -187,6 +187,12 @@ master superblock.
Clear the contents of the inode
.IR file .
.TP
+.I dirsearch filespec filename
+Search the directory
+.I filespec
+for
+.IR filename .
+.TP
.I dump [-p] filespec out_file
Dump the contents of the inode
.I filespec
@@ -199,6 +205,16 @@ option is given set the owner, group and permissions information on
to match
.IR filespec .
.TP
+.I dx_hash [-h hash_alg] [-s hash_seed] filename
+Calculate the directory hash of
+.IR filename .
+The hash algorithm specified with
+.I -h
+may be "legacy" "half_md4" or "tea".
+The hash seed specified with
+.I -s
+must be in UUID format.
+.TP
.I dump_extents [-n] [-l] filespec
Dump the the extent tree of the inode
.IR filespec .
@@ -264,6 +280,11 @@ Free the inode specified by
Print a list of commands understood by
.BR debugfs .
.TP
+.I htree_dump filespec
+Dump the hash-indexed directory
+.IR filespec ,
+showing its tree structure.
+.TP
.I icheck block ...
Print a listing of the inodes which use the one or more blocks specified
on the command line.
next reply other threads:[~2011-05-11 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 16:49 Eric Sandeen [this message]
2011-05-15 3:39 ` [PATCH] debugfs: document htree-related commands in man page Ted 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=4DCABE03.7040300@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.