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
12

DESCRIPTION

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

OPTIONS

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

EXAMPLES

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

DIAGNOSTICS

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

AUTHOR

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