fsck_cs(8) [osx man page]
FSCK_CS(8) BSD System Manager's Manual FSCK_CS(8) NAME
fsck_cs -- verify and repair CoreStorage logical volume groups SYNOPSIS
fsck_cs -q device ... fsck_cs -p device ... fsck_cs [-y | -n] [-x | -g] [-l logfile] device ... DESCRIPTION
The fsck_cs utility verifies and repairs CoreStorage logical volume group metadata. The device parameter(s) should be path(s) to the "raw" (character special) disk device(s) such as /dev/rdisk1s1 that constitute the CoreStor- age logical volume group. If you specify a "non-raw" (block special) path such as /dev/disk1s1, or just the disk name such as disk1s1, it will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -q Performs a "quick" check and indicates if any corruptions were found via the exit status. In this mode stale MLV segments are not checked, nor is proactive MLV mirror scrubbing performed. -p Operates in "preen" mode. MLV mirror blocks are repaired where necessary. Newer transactions may be invalidated to force a roll-back to an older, but consistent, filesystem state. -y Causes fsck_cs to assume "yes" as the answer to all questions. In other words, always attempt to repair any errors that are found. -n Causes fsck_cs to assume "no" as the answer to all questions. In other words, never attempt to repair any errors that are found. -x Causes fsck_cs to produce its output in an XML-like (plist) format. This option is used when another application with a graphical user interface (like Mac OS X Disk Utility) is invoking the fsck_cs tool and processing the output. -g Causes fsck_cs to produce its output in GUI-compatible form. This is similar in usage to the -x option. -l logfile Reproduce all console output, as well as additional status and error messages, to the specified file. Alternatively device can be specified as the UUID of the CoreStorage logical volume group or as the name of a CoreStorage-hosted logical vol- ume within that group, causing fsck_cs to derive the constituent raw device(s) from the IORegistry. In these cases you must indicate what object is being supplied to identify the logical volume group: --pv the component CoreStorage physical volume(s) directly --uuid the CoreStorage logical volume group (as a UUID) --lv a CoreStorage logical volume (as a device name) DIAGNOSTICS
The fsck_cs utility exits with 0 if no corruption was detected or if all corruptions were repaired, and with >0 if any unrepaired corruption remains. BUGS
fsck_cs does not perform an exhaustive validation, nor is it able to fix many of the inconsistencies that it does detect. HISTORY
The fsck_cs utility first appeared along with CoreStorage in Mac OS X 10.7.0. Darwin July 22, 2011 Darwin
Check Out this Related Man Page
FSCK_EXFAT(8) BSD System Manager's Manual FSCK_EXFAT(8) NAME
fsck_exfat -- Verify and repair ExFAT file systems. SYNOPSIS
fsck_exfat -q device ... fsck_exfat [-f] [-p] [-y | -n] [-g | -x] [-d] device ... DESCRIPTION
The fsck_exfat utility verifies and repairs ExFAT file systems. The first form of fsck_exfat quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck_exfat checks the specified file systems and tries to repair all detected problems, requesting confirmation before making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this default behavior. The device parameter(s) should be a path to a "raw" disk device (a character special device), such as /dev/rdisk1s1. If you specify a "non- raw" path (a block special device) such as /dev/disk1s1, or just the disk name such as disk1s1, they will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -q Causes fsck_exfat to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -f This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -p Preen the specified file systems. This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -y Causes fsck_exfat to assume yes as the answer to all questions. It will attempt to repair all problems that are found. -n Causes fsck_exfat to assume no as the answer to all questions. The device will be opened read-only, and no repairs will be made. -g Causes fsck_exfat to produce its output in GUI-compatible form. Each message is printed as a tuple containing the kind of mes- sage, the message string, and number of parameters to the message string. Any parameters to the message string are printed on subsequent lines. The message string uses NSLog-like substitutions. This output format is used by applications such as Disk Utility. -x Causes fsck_exfat to produce its output in an XML-like form. Each message is printed as a plist(5) containing a message type, verbosity, message number, and message string. The message string uses NSLog-like substitutions. For message strings that contain parameters, an array of dictionaries is output. This output format is used by applications such as Disk Utility. It may be used by other kinds of applications which wish to parse the output of fsck_exfat. -d Causes fsck_exfat to produce extra debugging output. This generally contains additional details about problems found. When writing bug reports for fsck_exfat, it is usually helpful to include the output generated from this option. SEE ALSO
mount_exfat(8), fsck(8) HISTORY
The fsck_exfat utility first appeared in Mac OS X 10.6.3. Darwin January 19, 2010 Darwin