|PVSCAN(8)||System Manager's Manual||PVSCAN(8)|
[ option_args ]
[ position_args ]
- When given specific device name arguments, pvscan --cache will only read the named devices.
- LVM udev rules and systemd services are used to initiate automatic device scanning.
- To prevent devices from being scanned by pvscan --cache,
add them to lvm.conf(5) devices/global_filter. The
devices/filter setting does not apply to system level scanning. For more
- If lvmetad is started or restarted after devices are visible, or if the global_filter has changed, then all devices must be rescanned for metadata with the command pvscan --cache.
- lvmetad does not cache older metadata formats, e.g. lvm1, and will be temporarily disabled if they are seen.
- To notify lvmetad about a device that is no longer present, the major and minor numbers must be given, not the path.
- pvscan auto-activation can be only done in combination with --cache.
- Auto-activation is designated by the "a" argument in --activate ay. This is meant to distinguish system generated commands from explicit user commands, although it can be used in any activation command. Whenever it is used, the auto_activation_volume_list is applied.
- Auto-activation is not yet supported for LVs that are part of partial or clustered volume groups.
[ -e|--exported ][ -n|--novolumegroup ][ -s|--short ][ -u|--uuid ][ COMMON_OPTIONS ]
[ -b|--background ][ -a|--activate ay ][ -j|--major Number ][ --minor Number ][ COMMON_OPTIONS ]
[ String|PV ... ]
[ --ignorelockingfailure ][ --reportformat basic|json ]
[ -d|--debug ][ -h|--help ][ -q|--quiet ][ -t|--test ][ -v|--verbose ][ -y|--yes ][ --commandprofile String ][ --config String ][ --driverloaded y|n ][ --longhelp ][ --profile String ][ --version ]
-a|--activate y|n|ayAuto-activate LVs in a VG when the PVs scanned have completed the VG. (Only ay is applicable.)
-b|--backgroundIf the operation requires polling, this option causes the command to return before the operation is complete, and polling is done in the background.
--cacheScan one or more devices and send the metadata to lvmetad.
--commandprofile StringThe command profile to use for command configuration. See lvm.conf(5) for more information about profiles.
--config StringConfig settings for the command. These override lvm.conf settings. The String arg uses the same format as lvm.conf, or may use section/field syntax. See lvm.conf(5) for more information about config.
-d|--debug ...Set debug level. Repeat from 1 to 6 times to increase the detail of messages sent to the log file and/or syslog (if configured).
--driverloaded y|nIf set to no, the command will not attempt to use device-mapper. For testing and debugging.
-e|--exportedOnly show PVs belonging to exported VGs.
-h|--helpDisplay help text.
--ignorelockingfailureAllows a command to continue with read-only metadata operations after locking failures.
--longhelpDisplay long help text.
-j|--major NumberThe major number of a device.
--minor NumberThe minor number of a device.
-n|--novolumegroupOnly show PVs not belonging to any VG.
--profile StringAn alias for --commandprofile or --metadataprofile, depending on the command.
-q|--quiet ...Suppress output and log messages. Overrides --debug and --verbose. Repeat once to also suppress any prompts with answer 'no'.
--reportformat basic|jsonOverrides current output format for reports which is defined globally by the report/output_format setting in lvm.conf. basic is the original format with columns and rows. If there is more than one report per command, each report is prefixed with the report name for identification. json produces report output in JSON format. See lvmreport(7) for more information.
-s|--shortShort listing format.
-t|--testRun in test mode. Commands will not update metadata. This is implemented by disabling all metadata writing but nevertheless returning success to the calling function. This may lead to unusual error messages in multi-stage operations if a tool relies on reading back metadata it believes has changed but hasn't.
-u|--uuidShow UUIDs in addition to device names.
-v|--verbose ...Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr.
--versionDisplay version information.
-y|--yesDo not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)
PVPhysical Volume name, a device path under /dev. For commands managing physical extents, a PV positional arg generally accepts a suffix indicating a range (or multiple ranges) of physical extents (PEs). When the first PE is omitted, it defaults to the start of the device, and when the last PE is omitted it defaults to end. Start and end range (inclusive): PV[:PE-PE]... Start and length range (counting from 0): PV[:PE+PE]...
StringSee the option description for information about the string content.
Size[UNIT]Size is an input number that accepts an optional unit. Input units are always treated as base two values, regardless of capitalization, e.g. 'k' and 'K' both refer to 1024. The default input unit is specified by letter, followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE. b|B is bytes, s|S is sectors of 512 bytes, k|K is kilobytes, m|M is megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes, e|E is exabytes. (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)lvm(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter. lvm(8) lvm.conf(5) lvmconfig(8)
|LVM TOOLS 2.02.176(2) (2017-11-03)||Red Hat, Inc.|