Signed-off-by: Wang Shilong <wangsl.f...@cn.fujitsu.com> Signed-off-by: Qu Wenruo <quwen...@cn.fujitsu.com> --- V1->V2: remove wrong copyright information --- man/btrfsck.8.in | 29 ++++++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/man/btrfsck.8.in b/man/btrfsck.8.in index 5004ba0..37b9cf6 100644 --- a/man/btrfsck.8.in +++ b/man/btrfsck.8.in @@ -1,11 +1,29 @@ .TH BTRFSCK 8 .SH NAME -btrfsck \- check a btrfs filesystem +btrfsck \- check and repair of a Btrfs filesystem .SH SYNOPSIS -.B btrfsck \fI device\fP +.B btrfsck [\fIoptions\fP] \fI<device>\fP .SH DESCRIPTION -\fBbtrfsck\fP is used to check a btrfs filesystem. -\fIdevice\fP is the device file where the filesystem is stored. +\fBbtrfsck\fP is used to check and optionally repair of a Btrfs filesystem. Now, it can only be run on an unmounted FS. Considering it is not well-tested +in real-life situations yet. if you have a broken Btrfs filesystem, btrfsck may not repair but cause aditional damages. \fI<device>\fP is the device file +where the filesystem is stored. + +\fIOptions\fP +.IP "\fB-s,--super \fI<superblock>\fP" 5 +specify which superblock copy that you want to use. +.IP "\fB--repair\fP" 5 +try to repair the filesystem. +.IP "\fB--init-csum-tree\fP" 5 +create a new CRC tree. +.IP "\fB--init-extent-tree\fP" 5 +create a new extent tree. + +.SH EXIT CODE +\fBbtrfsck\fR will return 0 exit code if no error happened. +Other exit code means some problems happened. + +.br +This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. .SH AVAILABILITY .B btrfsck is part of btrfs-progs. Btrfs is currently under heavy development, @@ -13,4 +31,5 @@ and not suitable for any uses other than benchmarking and review. Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for further details. .SH SEE ALSO -.BR mkfs.btrfs (8) +.BR mkfs.btrfs (8), +.BR btrfs (8) -- 1.8.0.1 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
