public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: wysochanski@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW man/vgrename.8 Date: Tue, 22 May 2007 02:51:00 -0000 [thread overview] Message-ID: <20070522025135.5826.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2007-05-22 02:51:34 Modified files: . : WHATS_NEW man : vgrename.8 Log message: Fix vgrename man page to include UUID and be more consistent with lvrename. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.619&r2=1.620 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/vgrename.8.diff?cvsroot=lvm2&r1=1.2&r2=1.3 --- LVM2/WHATS_NEW 2007/05/21 10:52:01 1.619 +++ LVM2/WHATS_NEW 2007/05/22 02:51:33 1.620 @@ -1,5 +1,6 @@ Version 2.02.26 - ================================= + Fix vgrename man page to include UUID and be consistent with lvrename. Add (experimental) OpenAIS support to clvmd. Remove symlinks if parent volume is deactivated. Fix and clarify vgsplit error messages. --- LVM2/man/vgrename.8 2002/11/18 14:02:24 1.2 +++ LVM2/man/vgrename.8 2007/05/22 02:51:33 1.3 @@ -8,11 +8,15 @@ [\-h/\-?/\-\-help] [\-t/\-\-test] [\-v/\-\-verbose] -OldVolumeGroupPath/\-Name NewVolumeGroupPath/\-Name +.IR OldVolumeGroup { Path | Name | UUID } +.IR NewVolumeGroup { Path | Name } .SH DESCRIPTION vgrename renames an existing (see .B vgcreate(8) -) volume group. +) volume group from +.IR OldVolumeGroup { Name | Path | UUID } +to +.IR NewVolumeGroup { Name | Path }. .SH OPTIONS See \fBlvm\fP for common options. .SH Examples @@ -20,6 +24,9 @@ volume group "vg02" to "my_volume_group". .TP "vgrename vg02 my_volume_group" does the same. +.TP +"vgrename Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 VolGroup00_tmp" renames a volume group with UUID Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 to the volume group named "VolGroup00_tmp". Using the UUID option to name a volume group may be useful in cases where one machine has two physical volumes, each with the same volume group name, but a separate volume group UUID (this situation will cause error messages with lvm commands). One way duplicate volume group names occur is if an old disk with a root volume is moved to a new machine with its own root volume. In this case, both volume groups may have the same name (for example, "VolGroup00"), but different UUIDs. +.TP .SH SEE ALSO .BR lvm (8), .BR vgchange (8),
reply other threads:[~2007-05-22 2:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070522025135.5826.qmail@sourceware.org \ --to=wysochanski@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: linkBe 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).