Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

thin_dump(8) [centos man page]

THIN_DUMP(8)						      System Manager's Manual						      THIN_DUMP(8)

thin_dump - dump thin provisioning metadata from device or file to standard output SYNOPSIS
thin_dump [options] {device|file} DESCRIPTION
thin_dump dumps binary thin provisioning metadata (optionally from alternate block; see option --metadata-snap) created by the device-map- per thin provisioning target on a device or file to standard output for analysis or postprocessing in either XML or human readable format. XML formated metadata can be fed into thin_restore (see thin_restore(8)) in order to put it back onto a metadata device (to process by the device-mapper target) or file. -f, --format {xml|human_readable} Print output in XML or human readable format. -r, --repair Repair the metadata whilst dumping it. -m, --metadata_snap [block#] Dump metadata snapshot created by device-mapper thin provisioning target. If block is not provided, access the default metadata snapshot created by the thin provisioning device-mapper target, else try the one at block#. See the thin provisioning target documentation on how to create or release a metadata snapshot and retrieve the block number from the kernel. -h, --help Print help and exit. -V, --version Output version information and exit. EXAMPLES
Dumps the thin provisioning metadata on logical volume /dev/vg/metadata to standard output in human readable format: thin_dump -f human_redable /dev/vg/metadata Dumps the thin provisioning metadata on logical volume /dev/vg/metadata to standard output in XML format: thin_dump /dev/vg/metadata Dumps the thin provisioning metadata snapshot on logical volume /dev/vg/metadata to standard output in human readable format (not process- able by thin_restore(8) ): thin_dump --format human_readable --metadata-snap /dev/vg/metadata DIAGNOSTICS
thin_dump returns an exit code of 0 for success or 1 for error. SEE ALSO
thin_check(8) thin_repair(8) thin_restore(8) thin_rmap(8) thin_metadata_size(8) AUTHOR
Joe Thornber <> Heinz Mauelshagen <> Red Hat, Inc. Thin Provisioning Tools THIN_DUMP(8)

Check Out this Related Man Page

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

disklabel -- manipulate and query an Apple Label disk label SYNOPSIS
disklabel -create disk-device [-msize=size] [property=value] [...] disklabel -status disk-device disklabel -properties disk-device [property[=value]] [...] disklabel -destroy disk-device DESCRIPTION
The disklabel utility manipulates ``Apple Label'' partition metadata. ``Apple Label'' partitions allow for a disk device to have a consis- tent name, ownership, and permissions across reboots, even though uses a dynamic pseudofilesystem for /dev. The ``Apple Label'' partition uses a set of metadata (as a plist) in a reserved area of the partition. This metadata describes the owner, name, and so forth. When -create is used, the -msize argument can specify the size of metadata area; the default is 128Kbytes. The default size unit is bytes, but the following suffixes may be used to multiply by the given factor: ``b'' (512), ``k'' (1024), ``m'' (1048576), and ``g'' (1073741824). Although any key-value pair can be specified for the properties, certain keys are used by the system: owner-uid The user (as either a string or numeric value) to own the device. owner-gid The group (as either a string or numeric value) associated with the device. owner-mode The permissions (as a numeric value) for the device. dev-name The name for the device. If the owner-uid and owner-gid properties are given as strings, the utility will attempt to look up the names (as users or groups, as appro- priate), and will store the numeric values in the metadata. If it cannot find the names, and the values are not given as numbers, it will print an error, and not store the key/value pairs in the metadata. The owner-mode property may be given in decimal, or in octal by using a preceding ``0'' (e.g., ``0666''). Any property may be forced to be treated as a string by enclosing it in double-quotation marks; bear in mind that shell escapes will probably be necessary in this sitation. The -properties directive can print out all keys (if no arguments are given), a requested set of keys (if a list of key names is given), or can modify (or add) keys (if a key-value pairs are given). also maintains a checksum of the metadata; the -status directive verifies this checksum. EXAMPLES
The following example will create a device with 1MByte of metadata area, owned by fred, with a device name of fred, and be writable by fred: disklabel -create /dev/rdisk1s1 -msize=1M owner-uid=fred dev-name=fred owner-mode=0644 The following example will then print out the key-value pairs from the above: disklabel -properties /dev/rdisk1s1 SEE ALSO
pdisk(8) BSD
September 3, 2004 BSD
Man Page

Featured Tech Videos