3
btrfs-image \- create/restore an image of the filesystem
6
[options] \fIsource\fP \fItarget\fP
9
is used to create an image of a btrfs filesystem. All data will be zeroed,
10
but metadata and the like is preserved.
12
is the special file corresponding to the device containing a btrfs filesystem.
13
(e.g \fI/dev/sdXX\fP).
15
is the image file that btrfs-image creates. When used with \fB-r\fP option,
16
\fBbtrfs-image\fP restores the image file from source into target.
20
Restore metadump image. By default, this fixes super's chunk tree, by
21
using 1 stripe pointing to primary device, so that file system can be
22
restored by running tree log reply if possible. To restore without
23
changing number of stripes in chunk tree check \fB-o\fP option.
26
compression level (0 ~ 9).
29
number of threads (1 ~ 32) to be used to process the image dump or restore.
32
use the old restore method, this does not fixup the chunk tree so the restored
33
file system will not be able to be mounted.
36
Sanitize the file names when generating the image. One \fB-s\fP means just
37
generate random garbage, which means that the directory indexes won't match up
38
since the hashes won't match with the garbage filenames. Using \fB-ss\fP will
39
calculate a collision for the filename so that the hashes match, and if it
40
can't calculate a collision then it will just generate garbage. The collision
41
calculator is very time and CPU intensive so only use it if you are having
42
problems with your file system tree and need to have it mostly working.
45
Walk all the trees manually and copy any blocks that are referenced. Use this
46
option if your extent tree is corrupted to make sure that all of the metadata is
50
is part of btrfs-tools. Btrfs is currently under heavy development,
51
and not suitable for any uses other than benchmarking and review.
52
Please refer to the btrfs wiki
53
http://btrfs.wiki.kernel.org for further details.
55
.BR btrfsck (8), mkfs.btrfs (8)