fsck.zfs.8: modernise

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Closes #12125
This commit is contained in:
наб 2021-05-26 14:34:00 +02:00 committed by Brian Behlendorf
parent a0372059b1
commit 55b6d4a3d8
1 changed files with 49 additions and 47 deletions

View File

@ -1,4 +1,3 @@
'\" t
.\" .\"
.\" CDDL HEADER START .\" CDDL HEADER START
.\" .\"
@ -19,53 +18,56 @@
.\" .\"
.\" CDDL HEADER END .\" CDDL HEADER END
.\" .\"
.\"
.\" Copyright 2013 Darik Horn <dajhorn@vanadac.com>. All rights reserved. .\" Copyright 2013 Darik Horn <dajhorn@vanadac.com>. All rights reserved.
.\" .\"
.TH FSCK.ZFS 8 "Mar 27, 2021" OpenZFS .Dd May 26, 2021
.Dt FSCK.ZFS 8
.SH NAME .Os
fsck.zfs \- Dummy ZFS filesystem checker. .
.Sh NAME
.SH SYNOPSIS .Nm fsck.zfs
.LP .Nd dummy ZFS filesystem checker
.BI "fsck.zfs [" "options" "] <" "dataset" ">…" .Sh SYNOPSIS
.Nm
.SH DESCRIPTION .Op Ar options
.LP .Ar dataset Ns No
\fBfsck.zfs\fR is a thin shell wrapper that at most checks the status of a .
dataset's container pool. It is installed by OpenZFS because some Linux .Sh DESCRIPTION
.Nm
is a thin shell wrapper that at most checks the status of a dataset's container pool.
It is installed by OpenZFS because some Linux
distributions expect a fsck helper for all filesystems. distributions expect a fsck helper for all filesystems.
.LP .Pp
If more than one \fIdataset\fR is specified, each is checked in turn If more than one
and results binary ored. .Ar dataset
is specified, each is checked in turn and the results binary-ored.
.SH OPTIONS .
.HP .Sh OPTIONS
All \fIoptions\fR are ignored. Ignored.
.
.SH "NOTES" .Sh NOTES
.LP ZFS datasets are checked by running
ZFS datasets are checked by running \fBzpool scrub\fR on the .Nm zpool Cm scrub
containing pool. An individual ZFS dataset is never checked on the containing pool.
independently of its pool, which is unlike a regular filesystem. An individual ZFS dataset is never checked independently of its pool,
which is unlike a regular filesystem.
.LP .Pp
However, the However, the
.BR fsck (8) .Xr fsck 8
interface still allows it to communicate some errors: interface still allows it to communicate some errors: if the
if the \fIdataset\fR is in a degraded pool, then \fBfsck.zfs\fR will .Ar dataset
return exit code 4 to indicate an uncorrected filesystem error. is in a degraded pool, then
.LP .Nm
Similarly, if the \fIdataset\fR is in a faulted pool and has a legacy will return exit code 4 to indicate an uncorrected filesystem error.
/etc/fstab record, then \fBfsck.zfs\fR will return exit code 8 to .Pp
indicate a fatal operational error. Similarly, if the
.Ar dataset
.SH "AUTHORS" is in a faulted pool and has a legacy
.LP .Pa /etc/fstab
Darik Horn <dajhorn@vanadac.com>. record, then
.Nm
.SH "SEE ALSO" will return exit code 8 to indicate a fatal operational error.
.BR fsck (8), .Sh SEE ALSO
.BR fstab (5), .Xr fstab 5 ,
.BR zpool-scrub (8) .Xr fsck 8 ,
.Xr zpool-scrub 8