Dne 16.9.2015 v 01:03 Chris Friesen napsal(a):
On 09/14/2015 12:05 PM, Chris Friesen wrote:
Hi,
I'm running a 3.10 kernel with LVM 2.02.95.
I'm running into a problem where activating snapshots can take quite a long
time, roughly one minute per 25GB of delta between the snapshot and the origin
volume. (See below for my test procedure.)
As a side question, currently we have a script which runs "vgchange -ay <vg>",
which will activate the VG.
This script appears to activate the LVs within the VG serially rather than in
parallel. Does it do any processing to determine in which order to activate
the LVs?
The reason I ask is that we have an overall timeout on the activate phase,
after which we'll put any un-activated LVs into an error state. It would be a
shame to try to activate a snapshotted LV first, and then timeout without
activating any of the non-snapshotted LVs.
Hi
Sorry, but there is no 'parallel' activation from lvm2 command - as lvm2 is
not multithreadded app (and is quite far away from that).
What you can do with recent versions of lvm2 - you could 'mark' (with
lvchange --setskipactivation) some LVs to be skipped from normal activation.
Then you could activate such skipped LVs with 'lvchange -ay -K'.
As said lvm2 has not been designed for this case.
(btw during whole activation - your access to VG is actually limited only for
'read-only')
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
