Manpage/btrfs-image

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
m (Protected "Manpage/btrfs-image": Counter-productive edit warring (‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)))
(remove content)
 
Line 1: Line 1:
=btrfs-image(8) manual page=
 
 
{{GeneratedManpage
 
{{GeneratedManpage
 
|name=btrfs-image}}
 
|name=btrfs-image}}
 
==NAME==
 
btrfs-image - create/restore an image of the filesystem
 
 
==SYNOPSIS==
 
 
<p><b>btrfs-image</b> [options] <em>&lt;source&gt;</em> <em>&lt;target&gt;</em></p>
 
==DESCRIPTION==
 
 
<p><b>btrfs-image</b> is used to create an image of a btrfs filesystem.
 
All data will be zeroed, but metadata and the like is preserved.
 
Mainly used for debugging purposes.</p>
 
<p>In the dump mode, source is the btrfs device/file and target is the output
 
file (use <em>-</em> for stdout).</p>
 
<p>In the restore mode (option -r), source is the dumped image and target is the btrfs device/file.</p>
 
==OPTIONS==
 
 
<dl>
 
<dt>
 
-r
 
<dd>
 
<p>
 
Restore metadump image. By default, this fixes super&#8217;s chunk tree, by
 
using 1 stripe pointing to primary device, so that file system can be
 
restored by running tree log reply if possible. To restore without
 
changing number of stripes in chunk tree check -o option.
 
</p>
 
 
<dt>
 
-c <em>&lt;value&gt;</em>
 
<dd>
 
<p>
 
Compression level (0 ~ 9).
 
</p>
 
 
<dt>
 
-t <em>&lt;value&gt;</em>
 
<dd>
 
<p>
 
Number of threads (1 ~ 32) to be used to process the image dump or restore.
 
</p>
 
 
<dt>
 
-o
 
<dd>
 
<p>
 
Use the old restore method, this does not fixup the chunk tree so the restored
 
file system will not be able to be mounted.
 
</p>
 
 
<dt>
 
-s
 
<dd>
 
<p>
 
Sanitize the file names when generating the image. One -s means just
 
generate random garbage, which means that the directory indexes won&#8217;t match up
 
since the hashes won&#8217;t match with the garbage filenames. Using -ss will
 
calculate a collision for the filename so that the hashes match, and if it
 
can&#8217;t calculate a collision then it will just generate garbage.  The collision
 
calculator is very time and CPU intensive so only use it if you are having
 
problems with your file system tree and need to have it mostly working.
 
</p>
 
 
<dt>
 
-w
 
<dd>
 
<p>
 
Walk all the trees manually and copy any blocks that are referenced. Use this
 
option if your extent tree is corrupted to make sure that all of the metadata is
 
captured.
 
</p>
 
 
<dt>
 
-m
 
<dd>
 
<p>
 
Restore for multiple devices, more than 1 device should be provided.
 
</p>
 
 
</dl>
 
==EXIT STATUS==
 
 
<p><b>btrfs-image</b> will return 0 if no error happened.
 
If any problems happened, 1 will be returned.</p>
 
==SEE ALSO==
 
 
<p>[[Manpage/mkfs.btrfs|mkfs.btrfs(8)]]</p>
 
[[Category:Manpage]]
 

Latest revision as of 12:30, 12 January 2022

Note: manual pages are located at read-the-docs site, please update your links.


Personal tools