shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity
94377dfd5e
lvm2/man/pvscan.8.in

77 lines
2.6 KiB
Groff
Raw Normal View History

Generate man pages from templates and include version. (romster)
2008-10-08 16:50:13 +04:00
.TH PVSCAN 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.SH NAME
pvscan \- scan all disks for physical volumes
.SH SYNOPSIS
.B pvscan
Place back some common options Until man pages are generated keep some common options with all commands.
2011-02-05 00:19:03 +03:00
.RB [ \-d | \-\-debug ]
.RB [ \-h | \-\-help ]
.RB [ \-v | \-\-verbose ]
.RB [ \-\-version ]
.RB [ \-\-ignorelockingfailure ]
Updating man pages
2011-01-28 19:03:38 +03:00
.RB [ \-e | \-\-exported ]
.RB [ \-n | \-\-novolumegroup ]
.RB [ \-s | \-\-short ]
.RB [ \-u | \-\-uuid ]
Switch pvscan --cache major:minor to --major --minor.
2012-03-06 06:30:49 +04:00
.BR
.B pvscan
.RB [ \-d | \-\-debug ]
.RB [ \-h | \-\-help ]
Update man pages Use one style for man pages.
2012-04-11 16:42:10 +04:00
.B \-\-cache
man: --activate ay and auto_activation_volume_list
2012-06-29 14:40:26 +04:00
.RB [ \-a | \-\-activate " " \fIay ]
tools: add -b/--background for pvscan --cache -aay Udev daemon has recently introduced a limit on the number of udev processes (there was no limit before). This causes a problem when calling pvscan --cache -aay in lvmetad udev rules which is supposed to activate the volumes. This activation is itself synced with udev and so it waits for the activation to complete before the pvscan finishes. The event processing can't continue until this pvscan call is finished. But if we're at the limit with the udev process count, we can't instatiate any more udev processes, all such events are queued and so we can't process the lvm activation event for which the pvscan is waiting. Then we're in a deadlock since the udev process with the pvscan --cache -aay call waits for the lvm activation udev processing to complete, but that will never happen as there's this limit hit with the number of udev processes. The process with pvscan --cache -aay actually times out eventually (3min or 30sec, depends on the version of udev). This patch makes it possible to run the pvscan --cache -aay in the background so the udev processing can continue and hence we can avoid the deadlock mentioned above.
2013-09-03 18:06:16 +04:00
.RB [ \-b | \-\-background ]
Switch pvscan --cache major:minor to --major --minor.
2012-03-06 06:30:49 +04:00
.RB [ \-\-major
Update man pages Use one style for man pages.
2012-04-11 16:42:10 +04:00
.I major
.B \-\-minor
.I minor
Switch pvscan --cache major:minor to --major --minor.
2012-03-06 06:30:49 +04:00
|
pvscan: use major:minor as short form of --major and --minor arg for pvscan --cache Before, pvscan recognized either: pvscan --cache --major <major> --minor <minor> or pvscan --cache <DevicePath> When the device is gone and we need to notify lvmetad about device removal, only --major/--minor works as we can't translate DevicePath into major/minor pair anymore. The device does not exist in the system and we don't keep DevicePath index in lvmetad cache to make the translation internally into original major/minor pair. It would be useless to keep this index just for this one exact case. There's nothing bad about using "--major <major> --minor <minor>", but it makes our life a bit harder when trying to make an interconnection with systemd units, mainly with instantiated services where only one and only one arg can be passed (which is encoded in the service name). This patch tries to make this easier by adding support for recognizing the "<major>:<minor>" as a shortcut for the longer form "--major <major> --minor <minor>". The rule here is simple: if the argument starts with "/", it's a DevicePath, otherwise it's a <major>:<minor> pair.
2013-10-22 15:52:18 +04:00
.IR DevicePath
|
.IR major:minor ]...
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.SH DESCRIPTION
Update man pages Use one style for man pages.
2012-04-11 16:42:10 +04:00
pvscan scans all supported LVM block devices in the system for
physical volumes.
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.SH OPTIONS
Updating man pages
2011-01-28 19:03:38 +03:00
See \fBlvm\fP(8) for common options.
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.TP
.BR \-e ", " \-\-exported
Only show physical volumes belonging to exported volume groups.
.TP
.BR \-n ", " \-\-novolumegroup
Only show physical volumes not belonging to any volume group.
.TP
.BR \-s ", " \-\-short
Short listing format.
.TP
.BR \-u ", " \-\-uuid
Some new features.
2002-11-18 17:04:08 +03:00
Show UUIDs (Uniform Unique Identifiers) in addition to device special names.
Add tentative documentation of pvscan --lvmetad to the pvscan manpage.
2012-02-26 12:45:07 +04:00
.TP
man: --activate ay and auto_activation_volume_list
2012-06-29 14:40:26 +04:00
.BR \-a ", " \-\-activate " " \fIay
Together with the information already cached in lvmetad, automatically activate
any logical volumes that become activatable after the scan done on one or more devices.
The logical volume to autoactivate is matched against the
man: refine lvm.conf and man page documentation for autoactivation feature
2013-06-14 11:36:56 +04:00
activation/auto_activation_volume_list set in lvm.conf. If this list is not set, then
all volumes are considered for autoactivation. The autoactivation is not yet
supported for logical volumes that are part of partial or clustered volume groups.
man: --activate ay and auto_activation_volume_list
2012-06-29 14:40:26 +04:00
.TP
tools: add -b/--background for pvscan --cache -aay Udev daemon has recently introduced a limit on the number of udev processes (there was no limit before). This causes a problem when calling pvscan --cache -aay in lvmetad udev rules which is supposed to activate the volumes. This activation is itself synced with udev and so it waits for the activation to complete before the pvscan finishes. The event processing can't continue until this pvscan call is finished. But if we're at the limit with the udev process count, we can't instatiate any more udev processes, all such events are queued and so we can't process the lvm activation event for which the pvscan is waiting. Then we're in a deadlock since the udev process with the pvscan --cache -aay call waits for the lvm activation udev processing to complete, but that will never happen as there's this limit hit with the number of udev processes. The process with pvscan --cache -aay actually times out eventually (3min or 30sec, depends on the version of udev). This patch makes it possible to run the pvscan --cache -aay in the background so the udev processing can continue and hence we can avoid the deadlock mentioned above.
2013-09-03 18:06:16 +04:00
.BR \-b ", " \-\-background
Run the command in the background.
.TP
pvscan: use format feature flags in lvmetad code Introduce FMT_OBSOLETE to identify pool metadata and use it and FMT_MDAS instead of hard-coded format names. Explain device accesses on pvscan --cache man page.
2014-01-08 06:13:13 +04:00
.BR \-\-cache " [" \-\-major " " \fImajor " " \-\-minor " " \fIminor " | " \fIDevicePath " | " \fImajor:minor " ]..."
Scan all devices for lvmetad if 'pvscan --cache' used without device list.
2012-03-03 22:32:53 +04:00
Scan one or more devices and instruct the lvmetad daemon to update its cached
state accordingly. Called internally by udev rules.
All devices listed explicitly are processed \fBregardless\fP of any device
doc: add a note about device filtering while lvmetad is used
2013-09-16 18:28:28 +04:00
filters set using \fBdevices/filter\fP configuration setting. To filter
devices even in this case, the \fBdevices/global_filter\fP must be used.
pvscan: use format feature flags in lvmetad code Introduce FMT_OBSOLETE to identify pool metadata and use it and FMT_MDAS instead of hard-coded format names. Explain device accesses on pvscan --cache man page.
2014-01-08 06:13:13 +04:00
If lvmetad has not yet cached any metadata or the filters have recently been
changed, then all devices may be scanned, effectively ignoring the rest of
the command line. Otherwise, if all the devices referenced on the command line
contain metadata in the default lvm2 format, other devices are not accessed.
If metadata written using the obsolete GFS pool format is encountered, this is
ignored and so lvmetad should not be used.
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.SH SEE ALSO
.BR lvm (8),
pvscan: use format feature flags in lvmetad code Introduce FMT_OBSOLETE to identify pool metadata and use it and FMT_MDAS instead of hard-coded format names. Explain device accesses on pvscan --cache man page.
2014-01-08 06:13:13 +04:00
.BR lvmetad (8),
Imported man pages from LVM1 with some quick LVM2 updates.
2002-01-04 23:35:19 +03:00
.BR pvcreate (8),
.BR pvdisplay (8)
Copy Permalink