Bug#544801: Unable to obtain global lock

Alasdair G Kergon agk at redhat.com
Thu Sep 3 01:12:07 UTC 2009

On Thu, Sep 03, 2009 at 01:51:24AM +0100, Alasdair G Kergon wrote:
> That sounds like a known upstream regression - that restriction should not
> apply to the global lock.  However, I've been on holiday and a quick
> check of WHATS_NEW suggests the fix has not yet been checked in.
> I'll add it as a blocker for the pending 2.02.52 release.
Yup - I've reproduced it upstream.

The fix (untested) should probably be something like changing
lib/locking/no_locking.c to:
  static int _readonly_lock_resource(struct cmd_context *cmd,
                                     const char *resource,
                                     uint32_t flags)
        if ((flags & LCK_TYPE_MASK) == LCK_WRITE &&
            (flags & LCK_SCOPE_MASK) == LCK_VG &&
            !(flags & LCK_CACHE) &&
            strcmp(resource, VG_GLOBAL))



More information about the pkg-lvm-maintainers mailing list