[Ocfs2-tools-devel] [PATCH 2/5] debugfs.ocfs2: Freshen up the manpage

Sunil Mushran sunil.mushran at oracle.com
Wed Sep 15 14:23:57 PDT 2010


Signed-off-by: Sunil Mushran <sunil.mushran at oracle.com>
---
 debugfs.ocfs2/debugfs.ocfs2.8.in |   22 +++++++++++++++++++---
 1 files changed, 19 insertions(+), 3 deletions(-)

diff --git a/debugfs.ocfs2/debugfs.ocfs2.8.in b/debugfs.ocfs2/debugfs.ocfs2.8.in
index 978741c..848dc52 100644
--- a/debugfs.ocfs2/debugfs.ocfs2.8.in
+++ b/debugfs.ocfs2/debugfs.ocfs2.8.in
@@ -1,4 +1,4 @@
-.TH "debugfs.ocfs2" "8" "February 2010" "Version @VERSION@" "OCFS2 Manual Pages"
+.TH "debugfs.ocfs2" "8" "September 2010" "Version @VERSION@" "OCFS2 Manual Pages"
 .SH "NAME"
 debugfs.ocfs2 \- OCFS2 file system debugger.
 .SH "SYNOPSIS"
@@ -87,8 +87,8 @@ by \fIOCFS2\fR are generated using the inode number and its generation
 number and can be decoded using the \fIdecode\fR command or used directly
 in place of an inode number in commands requiring a \fIfilespec\fR. Like
 inode numbers, locknames need to be enclosed in angle brackets, e.g.,
-<M000000000000000040c40c044069cf>. To generate a lockname for a given object,
-use the \fIencode\fR command.
+<M000000000000000040c40c044069cf>. Use the \fIencode\fR command to generate
+all possible locknames for an object.
 
 .SH "COMMANDS"
 This is a list of the commands which debugfs.ocfs2 supports.
@@ -147,6 +147,22 @@ timestamps and permissions information on \fIoutfile\fR to match
 those of \fIfilespec\fR.
 
 .TP
+\fIdx_dump filespec\fR
+Display the indexed directory information for the given directory.
+
+.TP
+\fIdx_leaf <block#>\fR
+Display the contents of the given indexed directory leaf block.
+
+.TP
+\fIdx_root <block#>\fR
+Display the contents of the given indexed directory root block.
+
+.TP
+\fIdx_space filespec\fR
+Display the directory free space list.
+
+.TP
 \fIencode filespec\fR
 Display the lockname for the \fIfilespec\fR.
 
-- 
1.7.0.4




More information about the Ocfs2-tools-devel mailing list