2014-04-02 08:29:29 +00:00
|
|
|
btrfs-debug-tree(8)
|
|
|
|
|
===================
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
btrfs-debug-tree - dump btrfs filesystem metadata into stdout
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2014-05-19 15:49:35 +00:00
|
|
|
*btrfs-debug-tree* [options] <device>
|
2014-04-02 08:29:29 +00:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2014-05-19 15:49:35 +00:00
|
|
|
*btrfs-debug-tree* is used to dump the whole tree of the given device.
|
2014-04-02 08:29:29 +00:00
|
|
|
|
|
|
|
|
This is maybe useful for analyzing filesystem state or inconsistence and has
|
|
|
|
|
a positive educational effect on understanding the internal structure.
|
|
|
|
|
<device> is the device file where the filesystem is stored.
|
|
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
|
-------
|
|
|
|
|
-e::
|
|
|
|
|
Print detailed extents info.
|
|
|
|
|
-d::
|
|
|
|
|
Print info of btrfs device and root tree dirs only.
|
|
|
|
|
-r::
|
|
|
|
|
Print info of roots only.
|
|
|
|
|
-b <block_num>::
|
|
|
|
|
Print info of the specified block only.
|
|
|
|
|
|
|
|
|
|
EXIT STATUS
|
|
|
|
|
-----------
|
2014-05-19 15:49:35 +00:00
|
|
|
*btrfs-debug-tree* will return 0 if no error happened.
|
2014-04-02 08:29:29 +00:00
|
|
|
If any problems happened, 1 will be returned.
|
|
|
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
`mkfs.btrfs`(8)
|
