Check a DOS (FAT-12/16/32) filesystem for consistency (QNX Neutrino)
chkdosfs [-npuy] device | mountpoint | file
- Answer "no" to all repair questions and prompts.
- Check and fix the filesystem non-interactively (i.e. "preen" mode).
- Perform unconditional check of the filesystem (regardless of the on-disk/dirty status).
- Answer "yes" to all repair questions and prompts.
- The device name hosting the DOS filesystem (e.g. /dev/hd0t6).
- The mountpoint of the DOS filesystem (e.g. /fs/hd0-dos).
- A regular file containing a DOS filesystem image.
The chkdosfs utility performs a consistency check on the specified DOS filesystem. This check consists of multiple passes over the filesystem.
If an error occurs, the action taken depends on the command-line options used. If -p was specified (typically to auto-check the filesystem at startup), no message is displayed and the default repair action is silently made. If either -n or -y was specified, a descriptive message is displayed and a "no" or "yes" response to the suggested action is automatically generated. Otherwise the user interactively decides on the repair action to make (the suggested default is indicated).
In order to perform repairs, chkdosfs requires write access to the device hosting the DOS filesystem. Normally, only root has permission for write access; if chkdosfs does not have such access, it will still check the filesystem but will operate as if the -n option had been specified.
By default, the chkdosfs utility checks an on-disk flag that's maintained by the filesystem that indicates to chkdosfs whether or not anything needs to be checked. This flag is usually updated when mounting or unmounting the filesystem. The -u option can be used to force the chkdosfs to run regardless of the state of this flag.
Check the filesystem on the DOS partition of a hard disk:
# chkdosfs /dev/hd0t11
Phase 1 - Read and compare FATs Phase 2 - Check cluster chains Phase 3 - Check directories Phase 4 - Check for lost files 1476784 kb used, 1010088 kb free, 24932 files, 2921 directories Filesystem is clean.
- The filesystem was checked and either no errors were detected or all such errors were repaired.
- The filesystem was not checked. This may be because the user interrupted the operation, a non-recoverable internal error such as insufficient memory occurred, or chkdosfs found an unrepairable error.
Wolfgang Solfrank, Martin Husemann