unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (HP-UX-11.11)
Page:
Section:
Apropos / Subsearch:
optional field



 fsck_vxfs(1M)						       fsck_vxfs(1M)




 NAME
      fsck - check and repair a VxFS file system

 SYNOPSIS
      /usr/sbin/fsck [-F vxfs] [-V] [-mnNpPyY] [-o full,nolog] [special... ]

 DESCRIPTION
      fsck checks VxFS file systems for consistency.  Because VxFS records
      pending file system updates in an intent log, fsck typically replays
      the intent log instead of doing a full structural file system check.
      You can use options (-o full or -y) to force a full structural file
      system check.

      If special is not specified, fsck prompts you with each file system
      listed in /etc/fstab to determine which file system to check, unless
      you specify -y or -Y, to automatically answer yes to the prompts.

    Options
      -F vxfs	     Specify the VxFS file system type.

      -m	     Check whether or not the file system is marked clean.
		     This option does not validate the file system.  The
		     file system could have been corrupted since it was
		     marked clean (for example, by a system crash), and if
		     so, a mount could fail.  In that case, a full fsck
		     would be required to clean it.  Use fsck -n to test for
		     file system corruption.

      -n|N	     Assume a "no" response to all prompts by fsck; do not
		     open the file system for writing, do not replay the
		     intent log.  A full file system check is performed.

      -p	     Produce messages that identify the device being
		     checked.

      -P	     With VxFS, -P is used by fsck by default; it does not
		     provide any functionality.

      -V	     Echo the completed command line, but do not execute the
		     command.  The command line is generated by
		     incorporating the user specified options and other
		     information derived from /etc/fstab.  This option
		     allows the user to verify the command line.

      -y|Y	     Assume a "yes" response to all prompts by fsck.
		     Additionally, if the file system requires a full file
		     system check after the log replay, or if the nolog
		     suboption causes the log replay to be skipped and the
		     file system is not clean, then a full file system check
		     is performed.




 Hewlett-Packard Company	    - 1 -   HP-UX Release 11i: November 2000






 fsck_vxfs(1M)						       fsck_vxfs(1M)




      -o	     Specify VxFS file system specific options.	 These
		     options can be a combination of the following in a
		     comma-separated list:

		     full      Perform a full file system check.

		     nolog     Do not perform log replay.  This option may
			       be used if the log area was physically
			       damaged.

		     Note: Use fsck -o full,nolog on clean file systems.  If
		     fsck -o full without nolog is run on a clean file
		     system, it first replays the intent log.  Since the
		     VX_FULLFSCK flag is set, an fsck does not update the
		     inode and extent maps before performing the full check,
		     so it reports inconsistencies.  Use the -n option to
		     verify file system inconsistencies.

      Because VxFS maintains an intent log, a complete check is generally
      not required; the default is to replay the intent log only.  If
      fsck_vxfs detects file system damage or the log replay operation
      detects damage, an indication that a complete check is required is
      placed in the super-block.  In this case, if the -y option was
      specified, the full check will be run after the log replay.  If the -y
      option was not used, fsck must be run again, with the -o full option
      to perform the full structural check.

      A full check looks for the following inconsistencies:

	   +  Blocks claimed by more than one inode or the free list.
	   +  Blocks claimed by an inode outside the range of the file
	      system.
	   +  Incorrect link counts.
	   +	 Size checks:
		   -  Incorrect number of blocks.
		   -  Directory entry format.
	   +	 Bad inode format.
	   +	 Blocks not accounted for anywhere.
	   +	 Directory checks:
		   -  File pointing to unallocated inode.
		   -  Inode number out of range.
		   -  Linkage to parent directory.
		   -  Hash chain linkage.
		   -  Free space count.
	   +	 Super-block checks:
		   -  Checksum mismatch.
		   -  More blocks for inodes than there are in the file
		      system.
	   +	 Structural Files:
		   -  Fileset headers.




 Hewlett-Packard Company	    - 2 -   HP-UX Release 11i: November 2000






 fsck_vxfs(1M)						       fsck_vxfs(1M)




		   -  Object Location Table (OLT).
		   -  Inode list files.
		   -  Inode allocation summary files.
		   -  Attribute files (including Access Control Lists).
		   -  Attribute link counts.
	   +	 Bad free block list format.
	   +	 Total free block and/or free inode count incorrect.

      Orphaned files and directories (allocated but unreferenced) are, with
      the user's agreement, reconnected by placing them in the lost+found
      directory.  The name assigned is the inode number.  The only
      restriction is that the directory lost+found must already exist in the
      file system's root directory.

 OUTPUT
      Structural errors discovered during a full check are displayed on
      standard output.	Responses required during a full check are read from
      standard input.

      The following return codes are used for the -m option for all devices
      other than the one used by the root file system:

	   0	   The file system is unmounted and clean.

	   32	   The file system is unmounted and needs checking.

	   33	   The file system is mounted.

	   34	   The stat of the device failed.

	   Other   The state could not be determined because of an error.

      The following return codes are used for the -m option for the device
      used by the root file system:

	   0	   The root file system is mounted read-only and is clean,
		   or the root file system is mounted read/write and
		   therefore is clean.

	   32	   The root file system is mounted read-only and needs
		   checking.

	   34	   The stat of the device failed.

	   Other   The state could not be determined because of an error.

      In most cases, fsck prints the following messages:

	   log replay in progress
	   replay complete - marking super-block as CLEAN




 Hewlett-Packard Company	    - 3 -   HP-UX Release 11i: November 2000






 fsck_vxfs(1M)						       fsck_vxfs(1M)




      If the file system is already clean, fsck prints the following message
      instead:

	   file system is clean - log replay is not required

      If fsck prints any other messages, a full structural check is needed.

 ERROR/DIAGNOSTICS
      All error messages that relate to the contents of a file system
      produced during a log replay are displayed on standard output.  All
      I/O failures and exit messages are displayed on standard error output.

 NOTES
      Checking the raw device is almost always faster.

      Unlike VxFS running on HP-UX 10.01 and 10.10, a full file system check
      does not always perform pending extended inode operations.  Some
      extended operations can only be processed when the file system is
      mounted.	A file system that has been marked CLEAN can still contain
      extended operations.

      If a structural flaw is detected, the VX_FULLFSCK flag will be set on
      the file system, without operator interaction.  If fsck was not
      invoked with the -y option, it must be reinvoked with the -y or -o
      full option to perform a full fsck.

      Large files (over two gigabytes) are supported on HP-UX 10.20 systems
      and above.  If fsck encounters a large file on an older OS version, it
      stops without completing the file system check.

 FILES
      /etc/fstab	  Default list of file systems to check.

 SEE ALSO
      fsck(1M), mkfs_vxfs(1M), ncheck_vxfs(1M).



















 Hewlett-Packard Company	    - 4 -   HP-UX Release 11i: November 2000