Zdenek Kabelac e02e5b0c5b activation: fix activation lock ...

Activation lock has a primary purpose to serialize locking of individual
LV in case there is no other protecting mechanism for parallel
execution.

However in the case an activated LV is composed from several other LVs,
noone should be able to manipulate with those LVs as well.

This patch add a very 'naive' global VG activation locking in this case.
In the future we may introduce smarter function detecting minimal closed
graph components if this will appear as bottleneck

Patch checks if the  VG Write lock is held - in this case we do not
need any more locking - command has exclusive access to VG.

In case we have clustered VG and we are activating an LV which does not
need other LVs - we also do not need any more locks.

In all other cases take respective lock - for single LV - use lvid,
for complex LVs  use vgname.

2017-10-11 14:24:28 +02:00

..

.exported_symbols

Pre-release cleanups.

2009-05-21 03:04:52 +00:00

cluster_locking.c

tidy: prefer not using else after return

2017-07-20 11:18:29 +02:00

external_locking.c

doc: change fsf address

2016-01-21 12:11:37 +01:00

file_locking.c

activation: fix locking resource name for activation lock

2017-10-11 14:24:28 +02:00

locking_types.h

doc: change fsf address

2016-01-21 12:11:37 +01:00

locking.c

tidy: prefer not using else after return

2017-07-20 11:18:29 +02:00

locking.h

activation: fix activation lock

2017-10-11 14:24:28 +02:00

lvmlockd.c

lvmlockd: activate mirror LVs in shared mode with cmirrord

2017-09-20 09:55:34 -05:00

lvmlockd.h

lvmlockd: print error about starting lock manager

2017-08-28 16:24:00 -05:00

Makefile.in

doc: change fsf address

2016-01-21 12:11:37 +01:00

no_locking.c

doc: change fsf address

2016-01-21 12:11:37 +01:00