Content-type: text/html; charset=UTF-8
FSCK.CRAMFS
Section: System Administration (8)Updated: April 2013
Index Return to Main Contents
NAME
fsck.cramfs - fsck compressed ROM file systemSYNOPSIS
fsck.cramfs [options] fileDESCRIPTION
fsck.cramfs is used to check the cramfs file system.OPTIONS
- -v, --verbose
- Enable verbose messaging.
- -b, --blocksize blocksize
- Use this blocksize, defaults to page size. Must be equal to what was set at creation time. Only used for --extract.
- --extract[=directory]
- Test to uncompress the whole file system. Optionally extract contents of the file to directory.
- -a
- This option is silently ignored.
- -y
- This option is silently ignored.
- -V, --version
- Display version information and exit.
- -h, --help
- Display help text and exit.
EXIT STATUS
-
- 0
- success
- 4
- file system was left uncorrected
- 8
- operation error, such as unable to allocate memory
- 16
- usage information was printed
SEE ALSO
mount(8), mkfs.cramfs(8)AVAILABILITY
The example command is part of the util-linux package and is available from Linux Kernel Archive
Index
This document was created by man2html, using the manual pages.
Time: 04:46:00 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8
FSCK.MINIX
Section: System Administration (8)Updated: June 2015
Index Return to Main Contents
NAME
fsck.minix - check consistency of Minix filesystemSYNOPSIS
fsck.minix [options] deviceDESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem.The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writing to it. Remember that the kernel can write to device when it searches for files.
The device name will usually have the following form:
-
/dev/hda[1-63] IDE disk 1 /dev/hdb[1-63] IDE disk 2 /dev/sda[1-15] SCSI disk 1 /dev/sdb[1-15] SCSI disk 2
If the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before exiting. There is no need to reboot after check.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for deletion.OPTIONS
- -l, --list
- List all filenames.
- -r, --repair
- Perform interactive repairs.
- -a, --auto
- Perform automatic repairs. This option implies --repair and serves to answer all of the questions asked with the default. Note that this can be extremely dangerous in the case of extensive filesystem damage.
- -v, --verbose
- Be verbose.
- -s, --super
- Output super-block information.
- -m, --uncleared
- Activate MINIX-like "mode not cleared" warnings.
- -f, --force
- Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is unmounted.
- -V, --version
- Display version information and exit.
- -h, --help
- Display help text and exit.
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem, fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
-
- 0
- No errors
- 3
- Filesystem errors corrected, system should be rebooted if filesystem was mounted
- 4
- Filesystem errors left uncorrected
- 7
- Combination of exit codes 3 and 4
- 8
- Operational error
- 16
- Usage or syntax error
AUTHORS
Linus TorvaldsError code values by Rik Faith
Added support for filesystem valid flag: Dr. Wettstein
Check to prevent fsck of mounted filesystem added by Daniel Quinlan
Minix v2 fs support by Andreas Schwab updated by Nicolai Langfeldt
Portability patch by Russell King
SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive
Index
This document was created by man2html, using the manual pages.
Time: 04:46:01 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8
FSCK
Section: System Administration (8)Updated: February 2009
Index Return to Main Contents
NAME
fsck - check and repair a Linux filesystemSYNOPSIS
fsck [-lsAVRTMNP] [-r [fd]] [-C [fd]] [-t fstype] [filesystem...] [--] [fs-specific-options]DESCRIPTION
fsck is used to check and optionally repair one or more Linux filesystems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of them.If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions:
-
- 0
- No errors
- 1
- Filesystem errors corrected
- 2
- System should be rebooted
- 4
- Filesystem errors left uncorrected
- 8
- Operational error
- 16
- Usage or syntax error
- 32
- Checking canceled by user request
- 128
- Shared-library error
The exit code returned when multiple filesystems are checked is the bit-wise OR of the exit codes for each filesystem that is checked.
In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux. The filesystem-specific checker is searched for in the PATH environment variable. If the PATH is undefined then fallback to "/sbin".
Please see the filesystem-specific checker manual pages for further details.
OPTIONS
- -l
- Create an exclusive flock(2) lock file (/run/fsck/<diskname>.lock) for whole-disk device. This option can be used with one device only (this means that -A and -l are mutually exclusive). This option is recommended when more fsck(8) instances are executed in the same time. The option is ignored when used for multiple devices or for non-rotating disks. fsck does not lock underlying devices when executed to check stacked devices (e.g. MD or DM) - this feature is not implemented yet.
- -r [fd]
-
Report certain statistics for each fsck when it completes. These statistics
include the exit status, the maximum run set size (in kilobytes), the elapsed
all-clock time and the user and system CPU time used by the fsck run. For
example:
/dev/sda1: status 0, rss 92828, real 4.002804, user 2.677592, sys 0.86186
GUI front-ends may specify a file descriptor fd, in which case the progress bar information will be sent to that file descriptor in a machine parsable format. For example:
/dev/sda1 0 92828 4.002804 2.677592 0.86186
- -s
- Serialize fsck operations. This is a good idea if you are checking multiple filesystems and the checkers are in an interactive mode. (Note: e2fsck(8) runs in an interactive mode by default. To make e2fsck(8) run in a non-interactive mode, you must either specify the -p or -a option, if you wish for errors to be corrected automatically, or the -n option if you do not.)
- -t fslist
-
Specifies the type(s) of filesystem to be checked. When the
-A
flag is specified, only filesystems that match
fslist
are checked. The
fslist
parameter is a comma-separated list of filesystems and options
specifiers. All of the filesystems in this comma-separated list may be
prefixed by a negation operator
'no'
or
'!',
which requests that only those filesystems not listed in
fslist
will be checked. If none of the filesystems in
fslist
is prefixed by a negation operator, then only those listed filesystems
will be checked.
Options specifiers may be included in the comma-separated fslist. They must have the format opts=fs-option. If an options specifier is present, then only filesystems which contain fs-option in their mount options field of /etc/fstab will be checked. If the options specifier is prefixed by a negation operator, then only those filesystems that do not have fs-option in their mount options field of /etc/fstab will be checked.
For example, if opts=ro appears in fslist, then only filesystems listed in /etc/fstab with the ro option will be checked.
For compatibility with Mandrake distributions whose boot scripts depend upon an unauthorized UI change to the fsck program, if a filesystem type of loop is found in fslist, it is treated as if opts=loop were specified as an argument to the -t option.
Normally, the filesystem type is deduced by searching for filesys in the /etc/fstab file and using the corresponding entry. If the type cannot be deduced, and there is only a single filesystem given as an argument to the -t option, fsck will use the specified filesystem type. If this type is not available, then the default filesystem type (currently ext2) is used.
- -A
-
Walk through the
/etc/fstab
file and try to check all filesystems in one run. This option is
typically used from the
/etc/rc
system initialization file, instead of multiple commands for checking
a single filesystem.
The root filesystem will be checked first unless the -P option is specified (see below). After that, filesystems will be checked in the order specified by the fs_passno (the sixth) field in the /etc/fstab file. Filesystems with a fs_passno value of 0 are skipped and are not checked at all. Filesystems with a fs_passno value of greater than zero will be checked in order, with filesystems with the lowest fs_passno number being checked first. If there are multiple filesystems with the same pass number, fsck will attempt to check them in parallel, although it will avoid running multiple filesystem checks on the same physical disk.
fsck does not check stacked devices (RAIDs, dm-crypt, ...) in parallel with any other device. See below for FSCK_FORCE_ALL_PARALLEL setting. The /sys filesystem is used to determine dependencies between devices.
Hence, a very common configuration in /etc/fstab files is to set the root filesystem to have a fs_passno value of 1 and to set all other filesystems to have a fs_passno value of 2. This will allow fsck to automatically run filesystem checkers in parallel if it is advantageous to do so. System administrators might choose not to use this configuration if they need to avoid multiple filesystem checks running in parallel for some reason - for example, if the machine in question is short on memory so that excessive paging is a concern.
fsck normally does not check whether the device actually exists before calling a filesystem specific checker. Therefore non-existing devices may cause the system to enter filesystem repair mode during boot if the filesystem specific checker returns a fatal error. The /etc/fstab mount option nofail may be used to have fsck skip non-existing devices. fsck also skips non-existing devices that have the special filesystem type auto.
- -C [fd]
- Display completion/progress bars for those filesystem checkers (currently only for ext[234]) which support them. fsck will manage the filesystem checkers so that only one of them will display a progress bar at a time. GUI front-ends may specify a file descriptor fd, in which case the progress bar information will be sent to that file descriptor.
- -M
- Do not check mounted filesystems and return an exit code of 0 for mounted filesystems.
- -N
- Don't execute, just show what would be done.
- -P
- When the -A flag is set, check the root filesystem in parallel with the other filesystems. This is not the safest thing in the world to do, since if the root filesystem is in doubt things like the e2fsck(8) executable might be corrupted! This option is mainly provided for those sysadmins who don't want to repartition the root filesystem to be small and compact (which is really the right solution).
- -R
- When checking all filesystems with the -A flag, skip the root filesystem. (This is useful in case the root filesystem has already been mounted read-write.)
- -T
- Don't show the title on startup.
- -V
- Produce verbose output, including all filesystem-specific commands that are executed.
- -?, --help
- Display help text and exit.
- --version
- Display version information and exit.
FILESYSTEM SPECIFIC OPTIONS
Options which are not understood by fsck are passed to the filesystem-specific checker!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.
FILES
/etc/fstabENVIRONMENT VARIABLES
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.
SEE ALSO
fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8), cramfsck(8), fsck.jfs(8), fsck.nfs(8), fsck.minix(8), fsck.msdos(8), fsck.vfat(8), fsck.xfs(8), reiserfsck(8)AUTHORS
Theodore Ts'o <tytso@mit.edu> Karel Zak <kzak@redhat.com>
AVAILABILITY
The fsck command is part of the util-linux package and is available from Linux Kernel Archive
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- FILESYSTEM SPECIFIC OPTIONS
- FILES
- ENVIRONMENT VARIABLES
- SEE ALSO
- AUTHORS
- AVAILABILITY
This document was created by man2html, using the manual pages.
Time: 04:46:01 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8
FSCK.FAT
Section: Maintenance Commands (8)Updated: 2015-04-16
Index Return to Main Contents
NAME
fsck.fat - check and repair MS-DOS filesystemsSYNOPSIS
fsck.fat [OPTIONS] DEVICEDESCRIPTION
fsck.fat verifies the consistency of MS-DOS filesystems and optionally tries to repair them.The following filesystem problems can be corrected (in this order):
- *
- FAT contains invalid cluster numbers. Cluster is changed to EOF.
- *
- File's cluster chain contains a loop. The loop is broken.
- *
- Bad clusters (read errors). The clusters are marked bad and they are removed from files owning them. This check is optional.
- *
- Directories with a large number of bad entries (probably corrupt). The directory can be deleted.
- *
- Files . and .. are non-directories. They can be deleted or renamed.
- *
- Directories . and .. in root directory. They are deleted.
- *
- Bad filenames. They can be renamed.
- *
- Duplicate directory entries. They can be deleted or renamed.
- *
- Directories with non-zero size field. Size is set to zero.
- *
- Directory . does not point to parent directory. The start pointer is adjusted.
- *
- Directory .. does not point to parent of parent directory. The start pointer is adjusted.
- *
- Start cluster number of a file is invalid. The file is truncated.
- *
- File contains bad or free clusters. The file is truncated.
- *
- File's cluster chain is longer than indicated by the size fields. The file is truncated.
- *
- Two or more files share the same cluster(s). All but one of the files are truncated. If the file being truncated is a directory file that has already been read, the filesystem check is restarted after truncation.
- *
- File's cluster chain is shorter than indicated by the size fields. The file is truncated.
- *
- Clusters are marked as used but are not owned by a file. They are marked as free.
Additionally, the following problems are detected, but not repaired:
- *
- Invalid parameters in boot sector
- *
- Absence of . and .. entries in non-root directories
When fsck.fat checks a filesystem, it accumulates all changes in memory and performs them only after all checks are complete. This can be disabled with the -w option.
OPTIONS
- -a
- Automatically repair the filesystem. No user intervention is necessary. Whenever there is more than one method to solve a problem, the least destructive approach is used.
- -A
- Use Atari variation of the MS-DOS filesystem. This is default if fsck.fat is run on an Atari, then this option turns off Atari format. There are some minor differences in Atari format: Some boot sector fields are interpreted slightly different, and the special FAT entries for end-of-file and bad cluster can be different. Under MS-DOS 0xfff8 is used for EOF and Atari employs 0xffff by default, but both systems recognize all values from 0xfff8...0xffff as end-of-file. MS-DOS uses only 0xfff7 for bad clusters, where on Atari values 0xfff0...0xfff7 are for this purpose (but the standard value is still 0xfff7).
- -b
- Make read-only boot sector check.
- -c PAGE
- Use DOS codepage PAGE to decode short file names. By default codepage 437 is used.
- -d PATH
- Delete the specified file. If more than one file with that name exist, the first one is deleted. This option can be given more than once.
- -f
- Salvage unused cluster chains to files. By default, unused clusters are added to the free disk space except in auto mode (-a).
- -l
- List path names of files being processed.
- -n
- No-operation mode: non-interactively check for errors, but don't write anything to the filesystem.
- -p
- Same as -a, for compatibility with other *fsck.
- -r
- Interactively repair the filesystem. The user is asked for advice whenever there is more than one approach to fix an inconsistency. This is the default mode and the option is only retained for backwards compatibility.
- -t
- Mark unreadable clusters as bad.
- -u PATH
- Try to undelete the specified file. fsck.fat tries to allocate a chain of contiguous unallocated clusters beginning with the start cluster of the undeleted file. This option can be given more than once.
- -v
- Verbose mode. Generates slightly more output.
- -V
- Perform a verification pass. The filesystem check is repeated after the first run. The second pass should never report any fixable errors. It may take considerably longer than the first pass, because the first pass may have generated long list of modifications that have to be scanned for each disk read.
- -w
- Write changes to disk immediately.
- -y
- Same as -a (automatically repair filesystem) for compatibility with other fsck tools.
EXIT STATUS
- 0
- No recoverable errors have been detected.
- 1
- Recoverable errors have been detected or fsck.fat has discovered an internal inconsistency.
- 2
- Usage error. fsck.fat did not access the filesystem.
FILES
- fsck0000.rec, fsck0001.rec, ...
- When recovering from a corrupted filesystem, fsck.fat dumps recovered data into files named 'fsckNNNN.rec' in the top level directory of the filesystem.
BUGS
Does not create . and .. files where necessary. Does not remove entirely empty directories. Should give more diagnostic messages. Undeleting files should use a more sophisticated algorithm.SEE ALSO
fatlabel(8)mkfs.fat(8)
HOMEPAGE
The home for the dosfstools project is its GitHub project pageAUTHORS
dosfstools were written by Werner Almesberger Roman Hodek and others. The current maintainer is Andreas Bombe
Index
This document was created by man2html, using the manual pages.
Time: 04:46:02 GMT, September 16, 2022 Content-type: text/html; charset=UTF-8
FSCK.NFS
Section: Maintenance Commands (8)Updated: May 2004
Index Return to Main Contents
NAME
fsck.nfs - Dummy fsck.nfs script that always returns success.SYNOPSIS
fsck.nfsDESCRIPTION
Debian GNU/Linux need this for when the root file system is on NFS: there is no way to find out if root is NFS mounted and we really want to do a "fsck -a /".EXIT CODE
The exit code returned by mount.nfs is always zero, meaning successful completion.SEE ALSO
fsck(8), fstab(5).
Index
This document was created by man2html, using the manual pages.
Time: 04:46:03 GMT, September 16, 2022
![[MAN] dpkg-shlibdeps](https://blogger.googleusercontent.com/img/a/AVvXsEitfznRjvReRJUdd4v4tRKeHPIiY6C4DkbiRpW4pB5OZ0x9kOjfQtTv9Fi2i8IjVLmzastSRdRDORdabWA1dlnhBibT-DKKkYqYuonPtC15h6_o6d10zPAjZ9qQkn4NfICnrEMX-4XvPMJpiSKALSp7wLwGfP05yapMjWQCy8wvQRVQyUokHrQllrbd=w72-h72-p-k-no-nu)
0 댓글