diff options
| author | Alasdair Kergon <agk@redhat.com> | 2012-03-02 18:09:46 +0000 |
|---|---|---|
| committer | Alasdair Kergon <agk@redhat.com> | 2012-03-02 18:09:46 +0000 |
| commit | d742cdf32713726d3c170c59846073d951a76a6f (patch) | |
| tree | b4f34b4c44d62e2b507cdda1b56ba14c57cf0f27 /doc/udev_assembly.txt | |
| parent | 7e35dfff3d556e0157fe5e2ed18b6123ebc4ba34 (diff) | |
| download | lvm2-d742cdf32713726d3c170c59846073d951a76a6f.tar.gz lvm2-d742cdf32713726d3c170c59846073d951a76a6f.tar.xz lvm2-d742cdf32713726d3c170c59846073d951a76a6f.zip | |
Change pvscan --lvmetad to pvscan --cache.
Diffstat (limited to 'doc/udev_assembly.txt')
| -rw-r--r-- | doc/udev_assembly.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/udev_assembly.txt b/doc/udev_assembly.txt index acf9d2c3..61864027 100644 --- a/doc/udev_assembly.txt +++ b/doc/udev_assembly.txt @@ -32,11 +32,11 @@ LVM For LVM, the crucial piece of the puzzle is lvmetad, which allows us to build up VGs from PVs as they appear, and at the same time collect information on what is -already available. A command, pvscan --lvmetad is expected to be used to +already available. A command, pvscan --cache is expected to be used to implement udev rules. It is relatively easy to make this command print out a list of VGs (and possibly LVs) that have been made available by adding any particular device to the set of visible devices. In othe words, udev says "hey, -/dev/sdb just appeared", calls pvscan --lvmetad, which talks to lvmetad, which +/dev/sdb just appeared", calls pvscan --cache, which talks to lvmetad, which says "cool, that makes vg0 complete". Pvscan takes this info and prints it out, and the udev rule can then somehow decide whether anything needs to be done about this "vg0". Presumably a table of devices that need to be activated |