2021-10-26 22:45:24 +00:00
|
|
|
fsck.btrfs(8)
|
|
|
|
|
=============
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
**fsck.btrfs** [-aApy] [<device>...]
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
**fsck.btrfs** is a type of utility that should exist for any filesystem and is
|
|
|
|
|
called during system setup when the corresponding ``/etc/fstab`` entries
|
2024-02-16 08:37:55 +00:00
|
|
|
contain non-zero value for *fs_passno*, see :manref:`fstab(5)` for more.
|
2021-10-26 22:45:24 +00:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
If you wish to check the consistency of a BTRFS filesystem or repair a damaged
|
2023-06-28 17:55:08 +00:00
|
|
|
filesystem, see :doc:`btrfs-check`. By default filesystem consistency is checked,
|
2021-10-26 22:45:24 +00:00
|
|
|
the repair mode is enabled via the *--repair* option (use with care!).
|
|
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
The options are all the same and detect if **fsck.btrfs** is executed in
|
|
|
|
|
non-interactive mode and exits with success, otherwise prints a message about
|
|
|
|
|
btrfs check.
|
|
|
|
|
|
|
|
|
|
EXIT STATUS
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
There are two possible exit codes returned:
|
|
|
|
|
|
|
|
|
|
0
|
|
|
|
|
No error
|
|
|
|
|
|
|
|
|
|
8
|
2022-12-07 20:00:25 +00:00
|
|
|
Operational error, e.g. device does not exist
|
2021-10-26 22:45:24 +00:00
|
|
|
|
|
|
|
|
FILES
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
|
|
``/etc/fstab``
|
|
|
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
|
2023-06-28 17:55:08 +00:00
|
|
|
:doc:`btrfs`,
|
2024-02-16 08:37:55 +00:00
|
|
|
:manref:`fsck(8)`,
|
|
|
|
|
:manref:`fstab(5)`
|
