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/pvremove.c
Date: Wed, 13 Dec 2006 18:40:00 -0000	[thread overview]
Message-ID: <20061213184023.27638.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk@sourceware.org	2006-12-13 18:40:23

Modified files:
	.              : WHATS_NEW 
	tools          : pvremove.c 

Log message:
	Add missing pvremove error message when device doesn't exist.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.520&r2=1.521
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/pvremove.c.diff?cvsroot=lvm2&r1=1.11&r2=1.12

--- LVM2/WHATS_NEW	2006/12/13 03:39:57	1.520
+++ LVM2/WHATS_NEW	2006/12/13 18:40:22	1.521
@@ -1,5 +1,6 @@
 Version 2.02.17 -
 ===================================
+  Add missing pvremove error message when device doesn't exist.
   When lvconvert allocates a mirror log, respect parallel area constraints.
   Use loop to iterate through the now-ordered policy list in _allocate().
   Check for failure to allocate just the mirror log.
--- LVM2/tools/pvremove.c	2006/11/17 02:45:51	1.11
+++ LVM2/tools/pvremove.c	2006/12/13 18:40:23	1.12
@@ -38,8 +38,8 @@
 	if (!(pv = pv_read(cmd, name, NULL, NULL, 1))) {
 		if (arg_count(cmd, force_ARG))
 			return 1;
-		else
-			return 0;
+		log_error("Physical Volume %s not found", name);
+		return 0;
 	}
 
 	/* orphan ? */


             reply	other threads:[~2006-12-13 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 18:40 agk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-28 19:35 agk
2006-11-17  2:45 agk
2006-04-05 22:24 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=20061213184023.27638.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).