o2image(8) [suse man page]

o2image(8)							OCFS2 Manual Pages							o2image(8)

NAME

       o2image - Copy or restore OCFS2 file system meta-data

SYNOPSIS

       o2image [-r] [-I] device image-file

DESCRIPTION

       o2image	copies	the  OCFS2  file  system  meta-data from the device to the specified image-file.  This image file contains the file system
       skeleton that includes the inodes, directory names and file names. It does not include any file data.

       This image file can be useful to debug certain problems that are not reproducible otherwise.  Like on-disk corruptions. It  could  also	be
       used to analyse the file system layout in an aging file system with an eye towards improving performance.

       As  the	image-file  contains a copy of all the meta-data blocks, it can be a large file.  By default, it is created in a packed format, in
       which all meta-data blocks are written back-to-back. With the -r option, the user could choose to have the file in the raw (or sparse) for-
       mat, in which the blocks are written to the same offset as they are on the device.

       debugfs.ocfs2 understands both formats.

       o2image	also  has  the option, -I, to restore the meta-data from the image file onto the device. This option will rarely be useful to end-
       users and has been written specifically for developers and testers.

OPTIONS

       -r     Copies the meta-data to the image-file in the raw format. Use this option only if the destination file system supports sparse files.
	      If unsure, do not use this option and let the tool create the image-file in the packed format.

       -I     Restores meta-data from the image-file onto the device. CAUTION: This option could corrupt the file system.

EXAMPLES

       [root@node1 ~]# o2image /dev/sda1 sda1.out
       Copies metadata blocks from /dev/sda1 device to sda1.out file

       [root@node1 ~] o2image -I /dev/sda1 sda1.out
       Use with CAUTION. Copies meta-data blocks from sda1.out onto the /dev/sda1 device.

SEE ALSO

       debugfs.ocfs2(8) fsck.ocfs2(8)

AUTHORS

       Oracle Corporation

COPYRIGHT

       Copyright (C) 2007, 2010 Oracle. All rights reserved.

Version 1.4.3							   February 2010							o2image(8)

fsck.ocfs2(8)							OCFS2 Manual Pages						     fsck.ocfs2(8)

NAME

       fsck.ocfs2 - Check an OCFS2 file system.

SYNOPSIS

       fsck.ocfs2 [ -fFGnuvVy ] [ -b superblock block ] [ -B block size ] device

DESCRIPTION

       fsck.ocfs2 is used to check an OCFS2 file system.

       device  is  the file where the file system is stored (e.g. /dev/sda1).  It will almost always be a device file but a regular file will work
       as well.

OPTIONS

       -b superblock block
	      Normally, fsck.ocfs2 will read the superblock from the first block of the device.  This option specifies an alternate block that the
	      superblock should be read from. (Use -r instead of this option.)

       -B blocksize
	      The  block  size, specified in bytes, can range from 512 to 4096.  A value of 0, the default, is used to indicate that the blocksize
	      should be automatically detected.

       -D     Optimize directories in filesystem. This option causes fsck.ocfs2 to coalesce the directory entries in order to improve the filesys-
	      tem performance.

       -f     Force checking even if the file system is clean.

       -F     By  default  fsck.ocfs2  will  check  with the cluster services to ensure that the volume is not in-use (mounted) on any node in the
	      cluster before proceeding.  -F skips this check and should only be used when it can be guaranteed that the volume is not mounted	on
	      any  node in the cluster. WARNING: If the cluster check is disabled and the volume is mounted on one or more nodes, file system cor-
	      ruption is very likely. If unsure, do not use this option.

       -G     Usually fsck.ocfs2 will silently assume inodes whose generation number does not match the generation number of the super	block  are
	      unused inodes.  This option causes fsck.ocfs2 to ask the user if these inodes should in fact be marked unused.

       -n     Give  the 'no' answer to all questions that fsck will ask.  This guarantees that the file system will not be modified and the device
	      will be opened read-only.  The output of fsck.ocfs2 with this option can be redirected to  produce  a  record  of  a  file  system's
	      faults.

       -r backup-number
	      mkfs.ocfs2  makes  upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol-
	      ume.  Use this option to specify the backup, 1 thru 6, to use to recover the superblock.

       -y     Give the 'yes' answer to all questions that fsck will ask.  This will repair all faults that fsck.ocfs2 finds but will not give  the
	      operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system.

       -v     This option causes fsck.ocfs2 to produce a very large amount of debugging output.

       -V     Print version information and exit.

EXIT CODE

       The exit code returned by fsck.ocfs2 is the sum of the following conditions:
	    0	 - No errors
	    1	 - File system errors corrected
	    2	 - File system errors corrected, system should
		   be rebooted
	    4	 - File system errors left uncorrected
	    8	 - Operational error
	    16	 - Usage or syntax error
	    32	 - fsck.ocfs2 canceled by user request
	    128  - Shared library error

SEE ALSO

       mkfs.ocfs2(8) debugfs.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2cb(7)

AUTHORS

       Oracle  Corporation.   This  man  page  entry  derives  some  text,  especially	the  exit code summary, from e2fsck(8) by Theodore Y. Ts'o
       <tytso@mit.edu>.

COPYRIGHT

       Copyright (C) 2004, 2010 Oracle. All rights reserved.

Version 1.4.3							   February 2010						     fsck.ocfs2(8)