Provided by: ocfs2-tools_1.4.3-1_i386
debugfs.ocfs2 - OCFS2 file system debugger.
debugfs.ocfs2 [-f cmdfile] [-R command] [-s backup] [-nwV?] [device]
debugfs.ocfs2 -l [tracebit ... [allow|off|deny]] ...
debugfs.ocfs2 -d, --decode lockname
debugfs.ocfs2 -e, --encode lock_type block_num [generation | parent]
The debugfs.ocfs2 program is an interactive file system debugger useful
in displaying on-disk OCFS2 filesystem structures on the specified
-d, --decode lockname
Display the information encoded in the lockname.
-e, --encode lock_type block_num [generation | parent]
Display the lockname obtained by encoding the arguments
-f, --file cmdfile
Executes the debugfs commands in cmdfile.
Specifies device is an o2image file created by o2image tool.
-l [tracebit ... [allow|off|deny]] ...
Control OCFS2 filesystem tracing by enabling and disabling trace
bits. Do debugfs.ocfs2 -l to get the list of all trace bits.
-R, --request command
Executes a single debugfs command.
-s, --superblock backup-number
mkfs.ocfs2 makes upto 6 backup copies of the superblock at
offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of
the volume. Use this option to specify the backup, 1 thru 6, to
use to open the volume.
Opens the filesystem in RW mode. By default the filesystem is
opened in RO mode.
Display version and exit.
Displays help and exit.
Many debugfs.ocfs2 commands take a filespec as an argument to specify
an inode (as opposed to a pathname) in the filesystem which is
currently opened by debugfs.ocfs2. The filespec argument may be
specified in two forms. The first form is an inode number or lockname
surrounded by angle brackets, e.g., <32>. The second form is a
pathname; if the pathname is prefixed by a forward slash (’/’), then it
is interpreted relative to the root of the filesystem which is
currently opened by debugfs.ocfs2. If not, the path is interpreted
relative to the current working directory as maintained by
debugfs.ocfs2, which can be modified using the command cd. If the
pathname is prefixed by a double forward slash (’//’), then it is
interpreted relative to the root of the system directory of the
filesystem opened by debugfs.ocfs2.
Locknames are specially formatted strings used by the file system to
uniquely identify objects in the filesystem. Most locknames used by
OCFS2 are generated using the inode number and its generation number
and can be decoded using the decode command or used directly in place
of an inode number in commands requiring a filespec. Like inode
numbers, locknames need to be enclosed in angle brackets, e.g.,
<M000000000000000040c40c044069cf>. To generate a lockname for a given
object, use the encode command.
This is a list of the commands which debugfs.ocfs2 supports.
bmap filespec logical_block
Display the physical block number corresponding to the logical
block number logical_block in the inode filespec.
Dump the contents of inode filespec to stdout.
Change the current working directory to filespec.
Change the root directory to be the directory filespec.
close Close the currently opened filesystem.
Display information obtained from ocfs2_controld.
curdev Show the currently open device.
Display the inode number encoded in the lockname.
Display the directory blocks associated with the given filespec.
dlm_locks [-f <file>] [-l] [<lockname(s)>]...
Display the status of all lock resources in the o2dlm domain
that the file system is a member of. This command expects the
debugfs filesystem to be mounted as mount -t debugfs debugfs
/sys/kernel/debug. Use lockname(s) to limit the output to the
given lock resources, -l to include contents of the lock value
block and -f <file> to specify a saved copy of
dump [-p] filespec outfile
Dump the contents of the inode filespec to the output file
outfile. If the -p is given, set the owner, group, timestamps
and permissions information on outfile to match those of
Display the lockname for the filespec.
Display the contents of the extent structure at block#.
Display the pathname for the inode specified by lockname or
inode#. This command does not display all the hard-linked paths
for the inode.
fs_locks [-f <file>] [-l] [-B] [<lockname(s)>]...
Display the status of all locks known by the file system. This
command expects the debugfs filesystem to be mounted as mount -t
debugfs debugfs /sys/kernel/debug. Use lockname(s) to limit the
output to the given lock resources, -B to limit the output to
only the busy locks, -l to include contents of the lock value
block and -f <file> to specify a saved copy of
Display the contents of the group descriptor at block#.
hb Display the contents of the heartbeat system file.
Print the list of commands understood by debugfs.ocfs2.
icheck block# ...
Display the inodes that use the one or more blocks specified on
the command line. If the inode is a regular file, also display
the corresponding logical block offset.
Change the current working directory of the debugfs.ocfs2
process to the directory on the native filesystem.
locate [<lockname>|<inode#>] ...
Display all pathnames for the inode(s) specified by locknames or
Display the contents of the journal for node node#.
ls [-l] filespec
Print the listing of the files in the directory filespec. The
-l flag will list files in the long format.
ncheck [<lockname>|<inode#>] ...
Open the filesystem on device.
rdump [-v] filespec outdir
Recursively dump directory filespec and all its contents
(including regular files, symbolic links and other directories)
into the outdir which should be an existing directory on the
Display the contents of the slotmap system file.
Display the contents of the inode structure for the filespec.
stats [-h] [-s backup-number]
Display the contents of the superblock. Use -s to display a
specific backup superblock. Use -h to hide the inode.
xattr [-v] <filespec>
Display extended attributes associated with the given filespec.
This tool has been modelled after debugfs, a debugging tool for ext2.
mkfs.ocfs2(8) fsck.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8)
ocfs2console(8) o2image(8) o2cb(7)
Copyright © 2004, 2009 Oracle. All rights reserved.