From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: chris.friesen@windriver.com
Subject: Re: [linux-lvm] Any way to speed up activation of volumes with snapshots?
Date: Wed, 16 Sep 2015 10:27:42 +0200 [thread overview]
Message-ID: <55F927FE.2040801@redhat.com> (raw)
In-Reply-To: <55F8A3BB.2020408@windriver.com>
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
next prev parent reply other threads:[~2015-09-16 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 18:05 [linux-lvm] Any way to speed up activation of volumes with snapshots? Chris Friesen
2015-09-14 18:46 ` Chris Friesen
2015-09-14 18:47 ` Zdenek Kabelac
2015-09-14 19:16 ` Chris Friesen
2015-09-14 19:41 ` Zdenek Kabelac
2015-09-15 8:41 ` Zdenek Kabelac
2015-09-15 16:54 ` Chris Friesen
2015-09-15 23:03 ` Chris Friesen
2015-09-16 8:27 ` Zdenek Kabelac [this message]
2015-09-16 15:30 ` Chris Friesen
2015-09-16 21:21 ` Zdenek Kabelac
2015-09-16 19:19 ` Chris Friesen
2015-09-16 21:20 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F927FE.2040801@redhat.com \
--to=zkabelac@redhat.com \
--cc=chris.friesen@windriver.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.