.br
.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]
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)