thin_dump(8)

1thin_dump(8)                System Manager's Manual               thin_dump(8)
2
3
4

NAME

6       thin_dump  -  dump  thin  provisioning  metadata from device or file to
7       standard output.
8

SYNOPSIS

10       thin_dump [options] {device|file}
11

DESCRIPTION

13       thin_dump dumps binary thin provisioning metadata (optionally from  al‐
14       ternate block; see option --metadata-snap) created by the device-mapper
15       thin provisioning target on a device or file  to  standard  output  for
16       analysis or postprocessing in either XML or human readable format.  XML
17       formated metadata can be fed into thin_restore (see thin_restore(8)) in
18       order  to put it back onto a metadata device (to process by the device-
19       mapper target) or file.
20
21       This tool cannot be run on live metadata unless the --metadata-snap op‐
22       tion is used.
23

OPTIONS

25       -h, --help
26              Print help and exit.
27
28       -V, --version
29              Print version information and exit.
30
31       -f, --format {xml|human_readable|custom}
32              Choose output format.
33
34           Custom formats are supported via shared library plugins.  They should be
35           specified as in this example:
36
37             $ thin_dump --format custom=mylib.so /dev/sda
38
39
40       -r, --repair
41              Repair the metadata whilst dumping it.
42
43       -m, --metadata-snap{=<block nr>}
44              Dump metadata snapshot.
45
46           If block is not provided, access the default metadata snapshot created by
47           the thin provisioning device-mapper target, else try the one at block nr.
48           See the thin provisioning target documentation on how to create or release
49           a metadata snapshot and retrieve the block number from the kernel.
50
51
52       --dev-id {natural}
53              Dump the specified device.
54
55           This option may be specified multiple times to select more than one thin
56           device.
57
58
59       --transaction-id {natural}
60              Override the transaction id given in the input xml.
61
62       --data-block-size {natural}
63              Override the data block size given in the input xml.
64
65       --nr-data-blocks {natural}
66              Override the nr data blocks given in the input xml.
67
68       --skip-mappings
69              Do not dump the mappings.
70
71       -o {xml file}
72              Specify a file for the output rather than writing to stdout.
73

EXAMPLES

75       Dumps the thin provisioning metadata on logical volume /dev/vg/metadata
76       to standard output in human readable format:
77
78           $ thin_dump -f human_readable /dev/vg/metadata
79
80       Dumps the thin provisioning metadata on logical volume /dev/vg/metadata
81       to standard output in XML format:
82
83           $ thin_dump /dev/vg/metadata
84
85       Dumps  the  thin  provisioning  metadata  snapshot  on  logical  volume
86       /dev/vg/metadata to standard output in human readable format (not  pro‐
87       cessable by thin_restore(8)):
88
89           $ thin_dump --format human_readable --metadata-snap /dev/vg/metadata
90
91

DIAGNOSTICS

93       thin_dump returns an exit code of 0 for success or 1 for error.
94

AUTHOR

100       Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <HeinzM@RedHat.com>
101
102
103
104System Manager's Manual       Device Mapper Tools                 thin_dump(8)