All of lore.kernel.org
 help / color / mirror / Atom feed
From: taka@sourceware.org <taka@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW tools/vgrename.c
Date: 23 Mar 2009 22:29:07 -0000	[thread overview]
Message-ID: <20090323222907.10430.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	taka at sourceware.org	2009-03-23 22:29:07

Modified files:
	.              : WHATS_NEW 
	tools          : vgrename.c 

Log message:
	Remove old metadata backup file after renaming vg.
	
	Author: Takahiro Yasui <tyasui@redhat.com>

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1069&r2=1.1070
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgrename.c.diff?cvsroot=lvm2&r1=1.58&r2=1.59

--- LVM2/WHATS_NEW	2009/03/23 21:56:32	1.1069
+++ LVM2/WHATS_NEW	2009/03/23 22:29:06	1.1070
@@ -9,6 +9,7 @@
   Fix unlocks in clvmd-corosync. Broken in 2.02.45.
   Fix error message when adding metadata directory to internal list fails.
   Fix size and error message of memory allocation at backup initialization.
+  Remove old metadata backup file after renaming vg.
 
 Version 2.02.45 - 3rd March 2009
 ================================
--- LVM2/tools/vgrename.c	2009/01/26 19:01:32	1.58
+++ LVM2/tools/vgrename.c	2009/03/23 22:29:06	1.59
@@ -149,6 +149,7 @@
 /******* FIXME Rename any active LVs! *****/
 
 	backup(vg);
+	backup_remove(cmd, vg_name_old);
 
 	unlock_vg(cmd, vg_name_new);
 	unlock_vg(cmd, vg_name_old);



             reply	other threads:[~2009-03-23 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 22:29 taka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-14 13:03 LVM2 ./WHATS_NEW tools/vgrename.c prajnoha
2008-04-30 14:34 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=20090323222907.10430.qmail@sourceware.org \
    --to=taka@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.