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

NAME

6       thin_check - validates thin provisioning metadata on a device or file
7

SYNOPSIS

9       thin_check [options] {device|file}
10

DESCRIPTION

12       thin_check checks thin provisioning metadata created by the device-map‐
13       per thin provisioning target on a device or file.
14
15       The tool cannot be run on live metadata unless the  --metadata-snapshot
16       option is used.
17

OPTIONS

19       -q, --quiet
20              Suppress output messages, return only exit code.
21
22       -h, --help
23              Print help and exit.
24
25       -V, --version
26              Output version information and exit.
27
28       --super-block-only
29              Only check the superblock.
30
31       --skip-mappings
32              Skip  checking  of  the block mappings which make up the bulk of
33              the metadata.
34
35       --ignore-non-fatal-errors
36              Will only return a non-zero exit code if it finds a fatal error.
37
38           An example of a nonfatal error is an incorrect data block reference count
39           causing a block to be considered allocated when it in fact isn't.  Ignoring
40           errors for a long time is not advised, you really should be using
41           thin_repair to fix them.
42
43
44       --clear-needs-check-flag
45              Clears the 'needs_check' flag in the superblock.
46
47           The kernel may set a flag to force the pool to be checked before it's next
48           activated.  Set this switch to clear the flag if the check is successful.
49           If the metadata check failed, the flag is not cleared and a thin_repair run
50           is needed to fix any issues. After thin_repair succeeded, you may run
51           thin_check again.
52
53
54       --metadata-snapshot, -m
55              Check the metadata snapshot.
56
57           This will check the devices tree and mappings in a metadata snapshot.
58           The snap does not contain space maps, so these will not be checked.  This
59           may be used on live metadata.
60
61
62       --auto-repair
63              Automatically repair any trivial issues found with the metadata.
64
65           Currently only fixes metadata leaks.
66
67
68       --override-mapping-root <block>
69              Specify a mapping root to use.
70
71           Don't use this.  This overrides what's specified in the superblock.  Only
72           use this if you really understand the metadata format and are trying to
73           recover damaged metadata.
74
75

EXAMPLE

77       Analyses thin provisioning metadata on logical volume /dev/vg/metadata:
78
79           $ thin_check /dev/vg/metadata
80
81       The device must not be actively used by the target when running.
82

DIAGNOSTICS

84       thin_check returns an exit code of 0 for success or 1 for error.
85

SEE ALSO

87       thin_dump(8), thin_repair(8), thin_restore(8), thin_rmap(8), thin_meta‐
88       data_size(8)
89

AUTHOR

91       Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <heinzm@redhat.com>
92
93
94
95System Manager's Manual       Device Mapper Tools                thin_check(8)
Impressum