On 2013-12-02T09:22:10, Ulrich Windl <[email protected]> wrote:
> >> No!
> >
> > Then it can't work. Exclusive activation only works for clustered volume
> > groups, since it uses the DLM to protect against the VG being activated
> > more than once in the cluster.
> Hi!
>
> Try it with "resource-agents-3.9.4-0.26.84": it works; with
> "resource-agents-3.9.5-0.6.26.11" it doesn't work ;-)
You thought it was working, but in fact it wasn't. ;-)
Or at least, not as you expected.
> You could argue that it never should have worked. Anyway: If you want
> to activate a VG on exactly one node you should not need cLVM; only if
> you man to activate the VG on multiple nodes (as for a cluster file
> system)...
You don't need cLVM to activate a VG on exactly one node. Correct. And
you don't. The cluster stack will never activate a resource twice.
You need cLVM if you want LVM2 to enforce that at the LVM2 level -
because it does this by getting a lock on the VG/LV, since otherwise
LVM2 has no way of knowing if the VG/LV is currently active somewhere
else. And this is what "exclusive=true" turns on.
If you don't want that to happen, exclusive=true is not what you want to
set.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
