public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW tools/vgchange.c
Date: Mon, 25 Oct 2010 10:40:00 -0000 [thread overview]
Message-ID: <20101025104015.27806.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2010-10-25 10:40:14
Modified files:
. : WHATS_NEW
tools : vgchange.c
Log message:
Don't take write lock in vgchange --refresh, --poll or --monitor.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1767&r2=1.1768
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgchange.c.diff?cvsroot=lvm2&r1=1.113&r2=1.114
--- LVM2/WHATS_NEW 2010/10/25 10:37:34 1.1767
+++ LVM2/WHATS_NEW 2010/10/25 10:40:13 1.1768
@@ -1,6 +1,7 @@
Version 2.02.75 -
=====================================
- Skip dm devices in scan if they contain only error targets.
+ Don't take write lock in vgchange --refresh, --poll or --monitor.
+ Skip dm devices in scan if they contain only error targets or are empty.
Fix strict-aliasing compile warning in partition table scanning.
Add an option to automatically extend snapshots through dmeventd.
Remove dependency on libm, floor() is replaced with integer algorithm.
--- LVM2/tools/vgchange.c 2010/08/17 16:25:35 1.113
+++ LVM2/tools/vgchange.c 2010/10/25 10:40:13 1.114
@@ -687,7 +687,10 @@
}
return process_each_vg(cmd, argc, argv,
- (arg_count(cmd, available_ARG)) ?
+ (arg_count(cmd, available_ARG) ||
+ arg_count(cmd, refresh_ARG) ||
+ arg_count(cmd, monitor_ARG) ||
+ arg_count(cmd, poll_ARG)) ?
0 : READ_FOR_UPDATE,
NULL,
&vgchange_single);
next reply other threads:[~2010-10-25 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 10:40 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-14 18:20 mbroz
2010-10-29 21:15 agk
2010-05-24 9:03 zkabelac
2010-05-24 8:59 zkabelac
2009-11-24 16:08 mbroz
2009-11-18 17:20 mbroz
2008-06-12 11:49 mbroz
2004-06-24 14:48 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=20101025104015.27806.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).