From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <55F98B17.8030504@windriver.com> Date: Wed, 16 Sep 2015 09:30:31 -0600 From: Chris Friesen MIME-Version: 1.0 References: <55F70C58.5010205@windriver.com> <55F8A3BB.2020408@windriver.com> <55F927FE.2040801@redhat.com> In-Reply-To: <55F927FE.2040801@redhat.com> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Any way to speed up activation of volumes with snapshots? Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Zdenek Kabelac , LVM general discussion and development On 09/16/2015 02:27 AM, Zdenek Kabelac wrote: > Dne 16.9.2015 v 01:03 Chris Friesen napsal(a): >> As a side question, currently we have a script which runs "vgchange -ay ", >> 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? > 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') Right...we're planning on testing out thin provisioning but I have to figure out a band-aid solution for products already in use. Just to clarify...what does your "access to VG is actually limited only for 'read-only'" mean exactly? Does it mean: 1) I only have read-only access to the LVs within the VG until all LVs in the VG are activated? or 2) I only have readonly access to the VG (so I can't add/remove/modify LVs) but I have read/write access to the LVs within the VG. Thanks, Chris