The program for debugging reiser4 filesystem.
debugfs.reiser4 [ options ] FILE
debugfs.reiser4 is reiser4 filesystem debug program. You can disscover the internal reiser4 filesystem structures by using it.
-V, --version
prints program version.
-?, -h, --help
prints program help.
-y, --yes
assumes an answer 'yes' to all questions.
-f, --force
forces debugfs to use whole disk, not block device or mounted partition.
-c, --cache N
sets tree cache node number to passed value. This affects very much behavior of libreiser4. It affects speed, tree allocation, etc.
-k, --cat
browses passed file like standard cat and ls programs.
-t, --print-tree
prints the internal tree.
-b, --print-block N
prints the block associated with the passed block number.
-n, --print-nodes FILE
prints all nodes that the passed file lies in.
-i, --print-file
prints all items that the passed file consists of.
-s, --print-super
prints the both super blocks: master super block and format specific one.
-j, --print-journal
prints the journal with not yet commited transactions (if any).
-a, --print-alloc
prints the block allocator data.
-d, --print-oid
prints the oid allocator data.
-P, --pack-metadata
fetches filesystem metadata and writes them to the standard output.
-U, --unpack-metadata
reads filesystem metadata stream from the stdandard input and constructs a new filesystem based on the metadata. debugfs.reiser4 --pack-metadata <FS1> | debugfs.reiser4 --unpack-metadata <FS2> and then debugfs.reiser4 --pack-metadata <FS2> produces a stream equivalent to the first one.
-p, --print-profile
prints the plugin profile. This is the set of default plugins used for all parts of a filesystem -- format, nodes, files, directories, hashes, etc. If --override is specified, then prints modified plugins.
-l, --print-plugins
prints all plugins libreiser4 knows about.
-o, --override TYPE=PLUGIN, ...
overrides the default plugin of the type "TYPE" by the plugin "PLUGIN" in the plugin profile.
debugfs.reiser4 -o nodeptr=nodeptr41,hash=rupasov_hash /dev/hda2
Report bugs to <[email protected]>
This manual page was written by Yury Umanets <[email protected]>