From: Zdenek Kabelac <zkabelac@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Any way to speed up activation of volumes with snapshots?
Date: Wed, 16 Sep 2015 23:20:18 +0200 [thread overview]
Message-ID: <55F9DD12.4080501@redhat.com> (raw)
In-Reply-To: <55F9C0B5.80002@windriver.com>
Dne 16.9.2015 v 21:19 Chris Friesen napsal(a):
> On 09/16/2015 02:27 AM, Zdenek Kabelac wrote:
>
>> Sorry, but there is no 'parallel' activation from lvm2 command - as lvm2 is not
>> multithreadded app (and is quite far away from that).
>
>
> Just had a weird thought. What would happen if I ran the "vgchange -ay"
> command, and then a few seconds later ran a bunch of "lvchange -ay" commands
> in parallel?
Since all of them are 'activation' requests - you just end with success
and everything should be activated.
Much more interesting case is - if you run in parallel activation
and deactivation :) - then the result depends on last executed command.
> Would that maybe let me activate non-snapshotted volumes even if the
> snapshotted volumes took a long time?
Yes - you could activate things in parallel this way - since every command has
separate udev cookie - so it waits on its set of LVs.
Zdenek
prev parent reply other threads:[~2015-09-16 21:20 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
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 [this message]
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=55F9DD12.4080501@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).