-.TH lctl-lfsck-start 8 "2016 Apr 1" Lustre "Lustre online fsck"
+.TH LCTL-LFSCK_START 8 "2017-05-13" Lustre "configuration utilities"
+.SH NAME
+lctl-lfsck_start \- start online Lustre File System Check
.SH SYNOPSIS
.br
-.B lctl lfsck_start \fR<-M | --device [MDT,OST]_device>
+.B lctl lfsck_start \fR[-M | --device [MDT,OST]_device]
\fR[-A | --all] [-c | --create-ostobj [on | off]]
- \fR[-C | --create-mttobj [on | off]]
+ \fR[-C | --create-mdtobj [on | off]]
+ \fR[-d | --delay-create-ostobj [on | off]]
\fR[-e | --error <continue | abort>] [-h | --help]
\fR[-n | --dryrun [on | off]] [-o | --orphan]
\fR[-r | --reset] [-s | --speed speed_limit]
.SH OPTIONS
.TP
.B -M, --device <MDT,OST_device>
-The MDT or OST device to start LFSCK/scrub on.
+The MDT or OST device to start LFSCK/scrub on. If "-M" option is not specified,
+it will select the available Lustre device on current server automatically.
+But under the following cases you need to specify the device (see "-M" option)
+explicitly: if there are multiple devices on current server those belong to
+different Lustre filesystems, or if "-A" option is not specified and there are
+multiple devices on current server.
.TP
.B -A, --all
-Start LFSCK on all nodes via the specified MDT device (see "-M" option) by
-single LFSCK command.
+Start LFSCK on all available devices in the system by single LFSCK command.
+Such LFSCK command can be executed on any MDT deivce in the system.
.TP
.B -c, --create-ostobj [on | off]
Create the lost OST-object for dangling LOV EA: 'off' (default) or 'on'. Under
the inconsistency but will not repair it. If 'on' is given, then LFSCK will
re-create the missed MDT-object.
.TP
+.B -d, --delay-create-ostobj [on | off]
+Delay to create the lost OST-object for dangling LOV EA until orphan OST-objects
+handled: 'off' (default) or 'on'. If both "--create-ostobj" and the delay option
+are 'on', then the LFSCK will NOT create the OST-object to repair dangling LOV
+EA unless all the OST-objects have been handled. It can avoid reparing dangling
+LOV EA incorrectly because of LOV EA corruption. The side-effect is that as long
+as one OST does not join the layout LFSCK or fail to complete the scanning, then
+reparing dangling LOV EA will be skipped. For a large system with a lot of OSTs,
+such condition may be a bit strict. The default value is 'off'.
+.TP
.B -e, --error <error_handle>
With error_handle as 'abort' then if the repair of a file is not possible, then
LFSCK will save the current position stop with an error. Otherwise the default
checks. By default there are at most 1024 outstanding requests.
.SH AVAILABILITY
-.B lctl
+.B lctl-lfsck-start
is part of the
-.BR Lustre (7)
+.BR lustre (7)
filesystem package.
.SH SEE ALSO
-.BR lustre (7),
+.BR lctl (8),
.BR lctl-lfsck-stop (8),
.BR lctl-lfsck-query (8)