|PVSCAN(8)||System Manager's Manual||PVSCAN(8)|
NAME¶pvscan - List all physical volumes
SYNOPSIS¶pvscan option_args [ option_args ] [ position_args ]
DESCRIPTION¶When called without the --cache option, pvscan lists PVs on the system, like pvs(8) or pvdisplay(8).
When the --cache and -aay options are used, pvscan records which PVs are available on the system, and activates LVs in completed VGs. A VG is complete when pvscan sees that the final PV in the VG has appeared. This is used by event-based system startup (systemd, udev) to activate LVs.
The four main variations of this are:
pvscan --cache device
If device is present, lvm adds a record that the PV on device is online. If device is not present, lvm removes the online record for the PV. In most cases, the pvscan will only read the named devices.
pvscan --cache -aay device...
This begins by performing the same steps as above. Afterward, if the VG for the specified PV is complete, then pvscan will activate LVs in the VG (the same as vgchange -aay vgname would do.)
This first clears all existing PV online records, then scans all devices on the system, adding PV online records for any PVs that are found.
pvscan --cache -aay
This begins by performing the same steps as pvscan --cache. Afterward, it activates LVs in any complete VGs.
To prevent devices from being scanned by pvscan --cache, add them
to lvm.conf(5) devices/global_filter. For more information,
lvmconfig --withcomments devices/global_filter
Auto-activation of VGs or LVs can be enabled/disabled using:
For more information, see:
lvmconfig --withcomments activation/auto_activation_volume_list
To disable auto-activation, explicitly set this list to an empty list, i.e. auto_activation_volume_list = [ ].
When this setting is undefined (e.g. commented), then all LVs are auto-activated.
USAGE¶Display PV information.
[ -n|--novolumegroup ]
[ -s|--short ]
[ -u|--uuid ]
[ COMMON_OPTIONS ]
Autoactivate a VG when all PVs are online.
[ -j|--major Number ]
[ --minor Number ]
[ COMMON_OPTIONS ]
Common options for command:
[ --reportformat basic|json ]
Common options for lvm:
[ -h|--help ]
[ -q|--quiet ]
[ -t|--test ]
[ -v|--verbose ]
[ -y|--yes ]
[ --commandprofile String ]
[ --config String ]
[ --driverloaded y|n ]
[ --lockopt String ]
[ --longhelp ]
[ --nolocking ]
[ --profile String ]
[ --version ]
Auto-activate LVs in a VG when the PVs scanned have completed the VG. (Only ay is applicable.)
Scan one or more devices and record that they are online.
The command profile to use for command configuration. See lvm.conf(5) for more information about profiles.
Config 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.
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).
If set to no, the command will not attempt to use device-mapper. For testing and debugging.
Only show PVs belonging to exported VGs.
Display help text.
Allows a command to continue with read-only metadata operations after locking failures.
Used to pass options for special cases to lvmlockd. See lvmlockd(8) for more information.
Display long help text.
The major number of a device.
The minor number of a device.
Only show PVs not belonging to any VG.
An alias for --commandprofile or --metadataprofile, depending on the command.
Suppress output and log messages. Overrides --debug and --verbose. Repeat once to also suppress any prompts with answer 'no'.
Overrides 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.
Short listing format.
Run 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.
Show UUIDs in addition to device names.
Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr.
Display version information.
Do not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)
Physical 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]...
See the option description for information about the string content.
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.)
ENVIRONMENT VARIABLES¶See lvm(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter.
SEE ALSO¶lvm(8) lvm.conf(5) lvmconfig(8)
vgcfgbackup(8) vgcfgrestore(8) vgchange(8) vgck(8) vgcreate(8) vgconvert(8) vgdisplay(8) vgexport(8) vgextend(8) vgimport(8) vgimportclone(8) vgmerge(8) vgmknodes(8) vgreduce(8) vgremove(8) vgrename(8) vgs(8) vgscan(8) vgsplit(8)
|LVM TOOLS 2.03.02(2) (2018-12-18)||Red Hat, Inc.|