NAME<\/a> pvck \u2212 Check metadata on physical volumes<\/p>\n pvck<\/b> option_args position_args<\/i> \u2212\u2212commandprofile<\/b> String<\/i> pvck checks and repairs LVM metadata on PVs.<\/p>\n Dump options metadata<\/b> metadata_all<\/b> metadata_search<\/b> metadata_area<\/b> Repair options There are cases where the PV UUID needs to be specified for the PV being repaired. It is specified using \u2212\u2212settings “pv_uuid= If a PV has no metadata areas and the pv_header is damaged, then the repair will not know to create no metadata areas during repair. It will by default repair metadata in mda1. To repair with no metadata areas, use -\u2212settings “mda_offset=0 mda_size=0”.<\/p>\n There are cases where repair should be run on all PVs in the VG (using the same metadata file): if all PVs in the VG are damaged, if using an old metadata version, or if a backup file is used instead of raw metadata (taken from pvck dump.)<\/p>\n Using \u2212\u2212repair is equivalent to running \u2212\u2212repairtype pv_header followed by -\u2212repairtype metadata.<\/p>\n \u2212\u2212repairtype pv_header<\/b> \u2212\u2212repairtype metadata<\/b> \u2212\u2212repairtype label_header<\/b> Settings<\/b> mda_num=1|2<\/b> metadata_offset=<\/b>bytes<\/i> mda_offset=<\/b>bytes<\/i> mda_size=<\/b>bytes<\/i> mda2_offset=<\/b>bytes<\/i> mda2_size=<\/b>bytes<\/i> pv_uuid=<\/b>uuid<\/i> device_size=<\/b>bytes<\/i> Check for metadata on a device<\/p>\n pvck<\/b> PV<\/i> …<\/p>\n [ COMMON_OPTIONS ]<\/p>\n –<\/p>\n Check and print LVM headers and metadata on a device<\/p>\n pvck \u2212\u2212dump headers<\/b>|metadata<\/b>|metadata_all<\/b>|metadata_search<\/b> PV<\/i><\/p>\n [ \u2212f<\/b>|\u2212\u2212file<\/b> String<\/i> ] –<\/p>\n Repair LVM headers or metadata on a device<\/p>\n pvck \u2212\u2212repairtype pv_header<\/b>|metadata<\/b>|label_header<\/b> PV<\/i><\/p>\n [ \u2212f<\/b>|\u2212\u2212file<\/b> String<\/i> ] –<\/p>\n Repair LVM headers and metadata on a device<\/p>\n pvck \u2212\u2212repair \u2212f<\/b>|\u2212\u2212file<\/b> String PV<\/i><\/p>\n [ \u2212\u2212settings<\/b> String<\/i> ] –<\/p>\n Common options for command:<\/p>\n [ \u2212\u2212labelsector<\/b> Number<\/i> ]<\/p>\n Common options for lvm:<\/p>\n [ \u2212d<\/b>|\u2212\u2212debug<\/b> ]
SYNOPSIS<\/a>
DESCRIPTION<\/a>
USAGE<\/a>
OPTIONS<\/a>
VARIABLES<\/a>
ENVIRONMENT VARIABLES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
[ option_args<\/i> ]<\/p>\n
\u2212\u2212config<\/b> String<\/i>
\u2212d<\/b>|\u2212\u2212debug
\u2212\u2212driverloaded y<\/b>|n
\u2212\u2212dump headers<\/b>|metadata<\/b>|metadata_all<\/b>|metadata_search
\u2212f<\/b>|\u2212\u2212file<\/b> String<\/i>
\u2212h<\/b>|\u2212\u2212help
\u2212\u2212labelsector<\/b> Number<\/i>
\u2212\u2212lockopt<\/b> String<\/i>
\u2212\u2212longhelp
\u2212\u2212nolocking
\u2212\u2212profile<\/b> String<\/i>
\u2212\u2212[pv]metadatacopies 0<\/b>|1<\/b>|2
\u2212q<\/b>|\u2212\u2212quiet
\u2212\u2212repair
\u2212\u2212repairtype pv_header<\/b>|metadata<\/b>|label_header
\u2212\u2212settings<\/b> String<\/i>
\u2212t<\/b>|\u2212\u2212test
\u2212v<\/b>|\u2212\u2212verbose
\u2212\u2212version
\u2212y<\/b>|\u2212\u2212yes<\/b><\/p>\nDESCRIPTION <\/a> <\/h2>\n
headers<\/b>
Print LVM on-disk headers and structures: label_header, pv_header, mda_header(s), and metadata text. Warnings are printed if any values are incorrect. The label_header and pv_header both exist in a 512 byte sector, usually the second sector of the device. An mda_header exists in a 512 byte sector at offset 4096 bytes. A second mda_header can optionally exist near the end of the device. The metadata text exists in an area (about 1MiB by default) immediately following the mda_header sector. The metadata text is checked but not printed (see other options).<\/p>\n
Print the current LVM VG metadata text (or save to a file), using headers to locate the latest copy of metadata. If headers are damaged, metadata may not be found (see metadata_search). Use \u2212\u2212settings “mda_num=2” to look in mda2 (the second mda at the end of the device, if used). The metadata text is printed to stdout or saved to a file with \u2212\u2212file.<\/p>\n
List all versions of VG metadata found in the metadata area, using headers to locate metadata. Full copies of all metadata are saved to a file with the \u2212\u2212file option. If headers are damaged, metadata may not be found (see metadata_search). Use \u2212\u2212settings “mda_num=2” as above. Use \u2212v to include descriptions and dates when listing metadata versions.<\/p>\n
List all versions of VG metadata found in the metadata area, searching common locations so metadata can be found if headers are damaged. Full copies of all metadata are saved to a file with the \u2212\u2212file option. To save one specific version of metadata, use \u2212\u2212settings “metadata_offset=
Save the entire text metadata area to a file without processing.<\/p>\n
\u2212\u2212repair<\/b>
Repair headers and metadata on a PV. This uses a metadata input file that was extracted by \u2212\u2212dump, or a backup file (from \/etc\/lvm\/backup). When possible, use metadata saved by \u2212\u2212dump from another PV in the same VG (or from a second metadata area on the PV).<\/p>\n
Repairs the header sector, containing the pv_header and label_header.<\/p>\n
Repairs the mda_header and metadata text. It requires the headers to be correct (having been undamaged or already repaired).<\/p>\n
Repairs label_header fields, leaving the pv_header (in the same sector) unchanged. (repairtype pv_header should usually be used instead.)<\/p>\n
The \u2212\u2212settings option controls or overrides certain dump or repair behaviors. All offset and size values in settings are in bytes (units are not recognized.) These settings are subject to change.<\/p>\n
Select which metadata area should be used. By default the first metadata area (1) is used. mda1 is always located at offset 4096. mda2, at the end of the device, often does not exist (it\u2019s not created by default.) If mda1 is erased, mda2, if it exists, will often still have metadata.<\/p>\n
Select metadata text at this offset. Use with metadata_search to print\/save one instance of metadata text.<\/p>\n
Refers to a metadata area (mda) location and size. An mda includes an mda_header and circular metadata text buffer. Setting this forces metadata_search look for metadata in the given area instead of the standard locations. When set to zero with repair, it indicates no metadata areas should exist.<\/p>\n
When repairing a pv_header, this forces a specific offset and size for mda2 that should be recorded in the pv_header.<\/p>\n
Specify the PV UUID of the device being repaired. When not specified, repair will attempt to determine the correct PV UUID by matching a device name in the metadata.<\/p>\n
data_offset=<\/b>bytes<\/i>
When repairing a pv_header, the device_size, data_offset, and pvid can all be specified directly, in which case these values are not taken from a metadata file (where they usually come from), and the metadata file can be omitted. data_offset is the starting location of the first physical extent (data), which follows the first metadata area.<\/p>\nUSAGE <\/a> <\/h2>\n
[ \u2212\u2212settings<\/b> String<\/i> ]
[ \u2212\u2212[pv]metadatacopies 0<\/b>|1<\/b>|2<\/b> ]
[ COMMON_OPTIONS ]<\/p>\n
[ \u2212\u2212settings<\/b> String<\/i> ]
[ COMMON_OPTIONS ]<\/p>\n
[ COMMON_OPTIONS ]<\/p>\n
[ \u2212h<\/b>|\u2212\u2212help<\/b> ]
[ \u2212q<\/b>|\u2212\u2212quiet<\/b> ]
[ \u2212t<\/b>|\u2212\u2212test<\/b> ]
[ \u2212v<\/b>|\u2212\u2212verbose<\/b> ]
[ \u2212y<\/b>|\u2212\u2212yes<\/b> ]
[ \u2212\u2212commandprofile<\/b> String<\/i> ]
[ \u2212\u2212config<\/b> String<\/i> ]
[ \u2212\u2212driverloaded y<\/b>|n<\/b> ]
[ \u2212\u2212lockopt<\/b> String<\/i> ]
[ \u2212\u2212longhelp<\/b> ]
[ \u2212\u2212nolocking<\/b> ]
[ \u2212\u2212profile<\/b> String<\/i> ]
[ \u2212\u2212version<\/b> ]<\/p>\nOPTIONS <\/a> <\/h2>\n