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.
16

OPTIONS

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

EXAMPLE

62       Analyses thin provisioning metadata on logical volume /dev/vg/metadata:
63
64           $ thin_check /dev/vg/metadata
65
66       The device must not be actively used by the target when running.
67

DIAGNOSTICS

69       thin_check returns an exit code of 0 for success or 1 for error.
70

SEE ALSO

72       thin_dump(8), thin_repair(8), thin_restore(8), thin_rmap(8), thin_meta‐
73       data_size(8)
74

AUTHOR

76       Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <heinzm@redhat.com>
77
78
79
80System Manager's Manual       Device Mapper Tools                thin_check(8)
Impressum