Home Explore Blog CI



man-pages

5th chunk of `fsck.man`
62afb7415d2590e7dd5038fdf9b99d3415b25bd910e4667f0000000100000cd2
  These options must not take arguments, as there is no way for fsck to be
       able to properly guess which options take arguments and which don’t.

       Options and arguments which follow the -- are treated as
       filesystem-specific options to be passed to the filesystem-specific
       checker.

       Please note that fsck is not designed to pass arbitrarily complicated
       options to filesystem-specific checkers. If you’re doing something
       complicated, please just execute the filesystem-specific checker
       directly. If you pass fsck some horribly complicated options and
       arguments, and it doesn’t do what you expect, don’t bother reporting it
       as a bug. You’re almost certainly doing something that you shouldn’t be
       doing with fsck. Options to different filesystem-specific fsck’s are not
       standardized.

ENVIRONMENT
       The fsck program’s behavior is affected by the following environment
       variables:

       FSCK_FORCE_ALL_PARALLEL
           If this environment variable is set, fsck will attempt to check all
           of the specified filesystems in parallel, regardless of whether the
           filesystems appear to be on the same device. (This is useful for
           RAID systems or high-end storage systems such as those sold by
           companies such as IBM or EMC.) Note that the fs_passno value is
           still used.

       FSCK_MAX_INST
           This environment variable will limit the maximum number of
           filesystem checkers that can be running at one time. This allows
           configurations which have a large number of disks to avoid fsck
           starting too many filesystem checkers at once, which might overload
           CPU and memory resources available on the system. If this value is
           zero, then an unlimited number of processes can be spawned. This is
           currently the default, but future versions of fsck may attempt to
           automatically determine how many filesystem checks can be run based
           on gathering accounting data from the operating system.

       PATH
           The PATH environment variable is used to find filesystem checkers.

       FSTAB_FILE
           This environment variable allows the system administrator to
           override the standard location of the /etc/fstab file. It is also
           useful for developers who are testing fsck.

       LIBBLKID_DEBUG=all
           enables libblkid debug output.

       LIBMOUNT_DEBUG=all
           enables libmount debug output.

FILES
       /etc/fstab

AUTHORS
       Theodore Ts’o <tytso@mit.edu>>, Karel Zak <kzak@redhat.com>

SEE ALSO
       fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8),
       fsck.cramfs(8), fsck.jfs(8), fsck.nfs(8), fsck.minix(8), fsck.msdos(8),
       fsck.vfat(8), fsck.xfs(8), reiserfsck(8)

REPORTING BUGS
       For bug reports, use the issue tracker at
       https://github.com/util-linux/util-linux/issues.

AVAILABILITY
       The fsck command is part of the util-linux package which can be
       downloaded from Linux Kernel Archive
       <https://www.kernel.org/pub/linux/utils/util-linux/>.

util-linux 2.39.1                  2023‐06‐14                           FSCK(8)

Title: fsck Environment Variables, Files, Authors, and Bug Reporting
Summary
This section details environment variables that affect fsck's behavior, including FSCK_FORCE_ALL_PARALLEL for parallel checks, FSCK_MAX_INST for limiting concurrent checkers, PATH for finding checkers, and FSTAB_FILE for overriding the fstab location. It also mentions debug options for libblkid and libmount. The section notes the /etc/fstab file, lists authors, provides related commands to see, explains how to report bugs, and specifies where to download the util-linux package containing fsck.