1LVSCAN(8) System Manager's Manual LVSCAN(8)
2
3
4
6 lvscan — scan (all disks) for Logical Volumes
7
9 lvscan [-a|--all] [-b|--blockdevice] [--commandprofile ProfileName]
10 [-d|--debug] [-h|--help] [--ignorelockingfailure] [-P|--partial]
11 [-v|--verbose]
12
14 lvscan scans all known volume groups or all supported LVM block devices
15 in the system for defined Logical Volumes. The output consists of one
16 line for each Logical Volume indicating whether or not it is active, a
17 snapshot or origin, the size of the device and its allocation policy.
18 Use lvs(8) or lvdisplay(8) to obtain more-comprehensive information
19 about the Logical Volumes.
20
22 See lvm(8) for common options.
23
24 --all Include information in the output about internal Logical Volumes
25 that are components of normally-accessible Logical Volumes, such
26 as mirrors, but which are not independently accessible (e.g. not
27 mountable). For example, after creating a mirror using lvcreate
28 -m1 --mirrorlog disk, this option will reveal three internal
29 Logical Volumes, with suffixes mimage_0, mimage_1, and mlog.
30
31 -b, --blockdevice
32 This option is now ignored. Instead, use lvs(8) or lvdisplay(8)
33 to obtain the device number.
34
35 --cache LogicalVolume
36 Applicable only when lvmetad(8) is in use (see also lvm.conf(5),
37 global/use_lvmetad). This command issues a rescan of physical
38 volume labels and metadata areas of all PVs that the logical
39 volume uses. In particular, this can be used when a RAID logical
40 volume becomes degraded, to update information about physical
41 volume availability. This is only necessary if the logical vol‐
42 ume is not being monitored by dmeventd (see lvchange(8), option
43 --monitor).
44
46 lvm(8), lvcreate(8), lvdisplay(8) lvs(8)
47
48
49
50Sistina Software UKLVM TOOLS 2.02.143(2)-RHEL6 (2016-12-13) LVSCAN(8)