NAME<\/a> thin_check<\/b> – validates thin provisioning metadata on a device or file<\/p>\n thin_check<\/b> [options<\/i>] {device|file}<\/p>\n thin_check<\/b> checks thin provisioning metadata created by the device-mapper thin provisioning target on a device or file.<\/p>\n The tool cannot be run on live metadata.<\/p>\n -q, –quiet<\/b><\/p>\n Suppress output messages, return only exit code.<\/p>\n -h, –help<\/b><\/p>\n Print help and exit.<\/p>\n -V, –version<\/b><\/p>\n Output version information and exit.<\/p>\n –super-block-only<\/b><\/p>\n Only check the superblock.<\/p>\n –skip-mappings<\/b><\/p>\n Skip checking of the block mappings which make up the bulk of the metadata.<\/p>\n –ignore-non-fatal-errors<\/b><\/p>\n Will only return a non-zero exit code if it finds a fatal error.<\/p>\n An example of a nonfatal error is an incorrect data block reference count Clears the \u2019needs_check\u2019 flag in the superblock.<\/p>\n The kernel may set a flag to force the pool to be checked before it\u2019s next Specify a mapping root to use.<\/p>\n Don\u2019t use this. This overrides what\u2019s specified in the superblock. Only Analyses thin provisioning metadata on logical volume \/dev\/vg\/metadata:<\/p>\n $ thin_check \/dev\/vg\/metadata<\/p>\n The device must not be actively used by the target when running.<\/p>\n thin_check<\/b> returns an exit code of 0 for success or 1 for error.<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
EXAMPLE<\/a>
DIAGNOSTICS<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
causing a block to be considered allocated when it in fact isn\u2019t. Ignoring
errors for a long time is not advised, you really should be using
thin_repair to fix them.
–clear-needs-check-flag<\/b><\/p>\n
activated. Set this switch to clear the flag if the check is successful.
If the metadata check failed, the flag is not cleared and a thin_repair run
is needed to fix any issues. After thin_repair succeeded, you may run
thin_check again.
–override-mapping-root
use this if you really understand the metadata format and are trying to
recover damaged metadata.<\/p>\nEXAMPLE <\/a> <\/h2>\n
DIAGNOSTICS <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n