Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

csgather(1)						    BSD General Commands Manual 					       csgather(1)

NAME

     csgather -- Gather CoreStorage metadata for diagnosis

SYNOPSIS

     csgather -G dir device ...
     csgather -r mountPoint [-o filename]

DESCRIPTION

     csgather gathers CoreStorage metadata for diagnosis.  It works in two modes.

     In the first mode where -G and a list of devices are provided, CoreStorage metadata on these list of devices will be collected.  The col-
     lected information includes the size and UUID of the CoreStorage logical and physical volumes, the name of the logical volumes, the wrapped
     (encrypted) volume key (which can only be decrypted by a brute-force attack), user name and user login image file.  No other user information
     (such as directory structure, file names, file content, etc) is collected.

     In the second mode where -r is provided, the encryption context which includes the wrapped volume key (which can only be decrypted by a
     brute-force attack), user name and user login image file will be collected.

     If the wrapped volume key is decrypted by a brute-force attack, the volume key used to encrypt data on CoreStorage Logical Volumes is in the
     clear.  It is not mathematically possible to derive the user's passphrase from the volume key.  The volume key is only useful when the
     attacker has access to the encrypted data in the CoreStorage Logical Volume, which are not collected by csgather.

     The following options are available:

     -G dir	    Gather all CoreStorage metadata and write into the specified directory.  The given directory must not already exist.

     -o filename    Specify the output file generated by the -r option.  If not given, use standard output.

     -r mountPoint  Find out the CoreStorage logical volume identified by the given mount point, and print its encryption context to the file
		    given in the -o option.

SEE ALSO

     csdiagnose(1)

HISTORY

     The csgather utility first appeared along with CoreStorage in OS X 10.10.0.

OS X
								   May 31, 2019 							      OS X
Man Page