mirror of
https://github.com/kdave/btrfs-progs
synced 2024-12-27 00:22:22 +00:00
48 lines
1.2 KiB
Groff
48 lines
1.2 KiB
Groff
.TH fsck.btrfs 8
|
|
.SH NAME
|
|
fsck.btrfs \- do nothing, successfully
|
|
.SH SYNOPSIS
|
|
.B fsck.btrfs
|
|
[\fB-aApy\fP]
|
|
[\fBdevice...\fP]
|
|
.SH DESCRIPTION
|
|
.B fsck.btrfs
|
|
is a type of utility that should exist for any filesystem and is
|
|
called during system setup when the corresponding
|
|
.BR /etc/fstab
|
|
entries contain non-zero value for
|
|
.BR fs_passno
|
|
, see
|
|
.BR fstab(5)
|
|
for more.
|
|
.PP
|
|
Traditional filesystems need to run their respective fsck utility in case the
|
|
filesystem was not unmounted cleanly and the log needs to be replayed before
|
|
mount. This is not needed for BTRFS. You should set fs_passno to 0.
|
|
.PP
|
|
If you wish to check the consistency of a BTRFS filesystem or repair a damaged
|
|
filesystem, see
|
|
.BR btrfs(8)
|
|
subcommand 'check'. By default the filesystem
|
|
consistency is checked, the repair mode is enabled via --repair option (use
|
|
with care!).
|
|
.SH OPTIONS
|
|
The options detect if \fBfsck.btrfs\fP is executed in non-interactive mode and exits
|
|
with success, otherwise prints a message about \fBbtrfs check\fP.
|
|
.SH EXIT CODE
|
|
There are two possible exit code returned:
|
|
.RS
|
|
.IP 0 5
|
|
No errors
|
|
.IP 8 5
|
|
Operational error, eg. device does not exist
|
|
.RE
|
|
.
|
|
.SH FILES
|
|
.IR /etc/fstab .
|
|
.SH SEE ALSO
|
|
.BR btrfs (8),
|
|
.BR fsck (8),
|
|
.BR fstab (5),
|
|
.\" btrfsck is intentionally left out
|