From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/lib/cache lvmcache.c
Date: 30 Jan 2008 16:18:39 -0000 [thread overview]
Message-ID: <20080130161839.11764.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2008-01-30 16:18:38
Modified files:
lib/cache : lvmcache.c
Log message:
only read labels once between each lock event
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/cache/lvmcache.c.diff?cvsroot=lvm2&r1=1.36&r2=1.37
--- LVM2/lib/cache/lvmcache.c 2008/01/30 13:59:58 1.36
+++ LVM2/lib/cache/lvmcache.c 2008/01/30 16:18:37 1.37
@@ -225,6 +225,16 @@
if (info->status & CACHE_INVALID)
return 0;
+ /*
+ * The caller must hold the VG lock to manipulate metadata.
+ * In a cluster, remote nodes sometimes read metadata in the
+ * knowledge that the controlling node is holding the lock.
+ * So if the VG appears to be unlocked here, it should be safe
+ * to use the cached value.
+ */
+ if (info->vginfo && !vgname_is_locked(info->vginfo->vgname))
+ return 1;
+
if (!(info->status & CACHE_LOCKED))
return 0;
next reply other threads:[~2008-01-30 16:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 16:18 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-01 21:58 LVM2/lib/cache lvmcache.c zkabelac
2012-03-01 21:57 zkabelac
2012-02-28 18:20 agk
2012-02-28 11:08 zkabelac
2012-02-28 10:10 zkabelac
2012-02-13 14:26 zkabelac
2011-12-08 23:18 agk
2011-04-21 13:15 zkabelac
2011-03-13 23:01 zkabelac
2010-10-25 13:33 zkabelac
2010-04-30 12:54 zkabelac
2010-03-16 19:06 agk
2010-01-11 19:12 snitzer
2010-01-11 19:08 snitzer
2009-04-24 12:03 mbroz
2008-11-28 15:51 agk
2008-06-06 12:43 agk
2008-04-15 14:54 agk
2007-11-05 17:12 agk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080130161839.11764.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.