mirror of
https://github.com/kdave/btrfs-progs
synced 2024-12-17 03:45:09 +00:00
7ffccaf0c3
A few minor benefits:
* editors set highliting according to the extensions
* web access to the git repository (github) renders the .asciidoc
files:
* we can link to them from the wiki
* the files are editable via browser and such editations can be
submitted for merge easily
Signed-off-by: David Sterba <dsterba@suse.cz>
52 lines
1.2 KiB
Plaintext
52 lines
1.2 KiB
Plaintext
fsck.btrfs(8)
|
|
=============
|
|
|
|
NAME
|
|
----
|
|
fsck.btrfs - do nothing, successfully
|
|
|
|
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
|
|
contain non-zero value for `fs_passno` , see `fstab`(5) for more.
|
|
|
|
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
|
|
filesystem, see `btrfs-check`(8). By default the filesystem
|
|
consistency is checked, the repair mode is enabled via '--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 code returned:
|
|
|
|
0::
|
|
No error
|
|
|
|
8::
|
|
Operational error, eg. device does not exist
|
|
|
|
FILES
|
|
-----
|
|
`/etc/fstab`
|
|
|
|
SEE ALSO
|
|
--------
|
|
`btrfs`(8),
|
|
`fsck`(8),
|
|
`fstab`(5),
|