hdik(8) [mojave man page]

hdik(8) 						    BSD System Manager's Manual 						   hdik(8)

NAME

     hdik -- lightweight tool to attach and mount disk images in-kernel

SYNOPSIS

     hdik imagefile [options]
     hdik -e device

DESCRIPTION

     hdik is a simple tool that can be used to attach disk images directly to the DiskImages driver.  The end result is functionally similar to
     passing -kernel to hdiutil(1)'s attach verb.  hdik does not rely upon the presence of DiskImages or other high-level frameworks.

     The DiskImages driver only supports a selection of disk image formats: UDRW, UDRO, UDZO, ULFO, SPARSE (UDSP).  It also supports shadow files.
     hdiutil(1)'s imageinfo verb indicates whether a particular image is kernel compatible.

     hdik requires root access to perform its functions.

     In the first form, an image to attach must be provided:

     imagefile	 path to the disk image file to attach.

     In its second form, hdik issues an eject command to the specified device.	The argument is the full device node path (e.g.  /dev/disk2). Any
     volumes mounted from the device must be unmounted first, or the command will fail.  See umount(8).

OPTIONS

     -shadow [shadowfile]
		 Use a shadow file in conjunction with the data in the image.  This option prevents modification of the original image and allows
		 read-only images to be used as read/write images.  When blocks are being read from the image, blocks present in the shadow file
		 override blocks in the base image.  When blocks are being written, the writes will be redirected to the shadow file.  If not
		 specified, -shadow defaults to <imagename>.shadow.  If the shadow file does not exist, it is created.

     -nomount	 Suppress automatic mounting of filesystems contained within the image.  This will result in /dev entries being created, but will
		 not mount any volumes.

     -drivekey keyname=value
		 Specify a key/value pair for the IOHDIXHDDrive object created (shows up in the IOKit registry of devices which is viewable with
		 ioreg(8)).

SEE ALSO

     hdiutil(1), diskarbitrationd(8), diskutil(8), umount(8), ioreg(8)

macOS								    20 Mar 2014 							     macOS

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.

       -i     Interactive mode - before writing out the image file print it's size and ask whether to proceed. This setting only applies when '-I'
	      is not specified. It can be useful when the file system holding the image is low on disk space and the user might need  to  free	up
	      space once the target image size is calculated.

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.6.4							  September 2010							o2image(8)