From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21722 invoked by alias); 2 Feb 2011 23:57:48 -0000 Received: (qmail 21700 invoked by uid 9447); 2 Feb 2011 23:57:48 -0000 Date: Wed, 02 Feb 2011 23:57:00 -0000 Message-ID: <20110202235748.21698.qmail@sourceware.org> From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/lib/locking cluster_locking.c Mailing-List: contact lvm2-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: lvm2-cvs-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00006.txt.bz2 CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2011-02-02 23:57:48 Modified files: lib/locking : cluster_locking.c Log message: a few more comments Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/cluster_locking.c.diff?cvsroot=lvm2&r1=1.52&r2=1.53 --- LVM2/lib/locking/cluster_locking.c 2011/02/02 23:39:39 1.52 +++ LVM2/lib/locking/cluster_locking.c 2011/02/02 23:57:48 1.53 @@ -342,10 +342,14 @@ * VG locks are just that: locks, and have no side effects * so we only need to do them on the local node because all * locks are cluster-wide. + * * Also, if the lock is exclusive it makes no sense to try to * acquire it on all nodes, so just do that on the local node too. - * One exception, is that P_ locks (except VG_SYNC_NAMES) /do/ get - * distributed across the cluster because they might have side-effects. + * + * P_ locks /do/ get distributed across the cluster because they might + * have side-effects. + * + * SYNC_NAMES and VG_BACKUP use the VG name directly without prefix. */ if (clvmd_cmd == CLVMD_CMD_SYNC_NAMES) { if (flags & LCK_LOCAL)