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/vgsplit.8 Date: Wed, 09 Apr 2008 14:39:00 -0000 [thread overview] Message-ID: <20080409143956.27996.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2008-04-09 14:39:55 Modified files: . : WHATS_NEW man : vgsplit.8 Log message: Update vgsplit man page to reflect lvnames on cmdline. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.838&r2=1.839 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/vgsplit.8.diff?cvsroot=lvm2&r1=1.7&r2=1.8 --- LVM2/WHATS_NEW 2008/04/09 13:47:13 1.838 +++ LVM2/WHATS_NEW 2008/04/09 14:39:55 1.839 @@ -1,6 +1,7 @@ Version 2.02.34 - =================================== - Update vgsplit to take "-n LogicalVolumeName" on the commandline. + Update vgsplit man page to reflect lvnames on the cmdline. + Update vgsplit to take "-n LogicalVolumeName" on the cmdline. Use clustered mirror log with pvmove in clustered VGs, if available. Fix some pvmove error status codes. Fix vgsplit error paths to release vg_to lock. --- LVM2/man/vgsplit.8 2008/01/22 02:48:52 1.7 +++ LVM2/man/vgsplit.8 2008/04/09 14:39:55 1.8 @@ -15,18 +15,21 @@ .IR type ] .RB [ -p | \-\-maxphysicalvolumes .IR MaxPhysicalVolumes ] +.RB [ \-n | \-\-name +.IR LogicalVolumeName ] .RB [ \-t | \-\-test ] .RB [ \-v | \-\-verbose ] SourceVolumeGroupName DestinationVolumeGroupName -PhysicalVolumePath [PhysicalVolumePath...] +[ PhysicalVolumePath ...] .SH DESCRIPTION .B vgsplit -moves -.IR PhysicalVolumePath (s) -from +moves one or more physical volumes from .I SourceVolumeGroupName into -.I DestinationVolumeGroupName\fP. +.I DestinationVolumeGroupName\fP. The physical volumes moved can be +specified either explicitly via \fIPhysicalVolumePath\fP, or implicitly by +\fB-n\fP \fILogicalVolumeName\fP, in which case only physical volumes +underlying the specified logical volume will be moved. If .I DestinationVolumeGroupName @@ -46,9 +49,13 @@ volume group attributes with an existing destination volume group is an error, and no split will occur. -Logical Volumes cannot be split between Volume Groups. -Each existing Logical Volume must be entirely on the Physical Volumes forming -either the source or the destination Volume Group. +Logical volumes cannot be split between volume groups. \fBVgsplit(8)\fP only +moves complete physical volumes: To move part of a physical volume, use +\fBpvmove(8)\fP. Each existing logical volume must be entirely on the physical +volumes forming either the source or the destination volume group. For this +reason, \fBvgsplit(8)\fP may fail with an error if a split would result in a +logical volume being split across volume groups. + .SH OPTIONS See \fBlvm\fP for common options. .SH SEE ALSO
next reply other threads:[~2008-04-09 14:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-09 14:39 wysochanski [this message] -- strict thread matches above, loose matches on Subject: below -- 2004-12-09 16:58 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=20080409143956.27996.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).