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/man vgsplit.8 Date: Thu, 17 Jan 2008 03:18:00 -0000 [thread overview] Message-ID: <20080117031818.30750.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2008-01-17 03:18:18 Modified files: man : vgsplit.8 Log message: Fixup vgsplit man page Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/vgsplit.8.diff?cvsroot=lvm2&r1=1.5&r2=1.6 --- LVM2/man/vgsplit.8 2008/01/16 17:14:56 1.5 +++ LVM2/man/vgsplit.8 2008/01/17 03:18:18 1.6 @@ -29,9 +29,24 @@ .I SourceVolumeGroupName into .I DestinationVolumeGroupName\fP. + If .I DestinationVolumeGroupName -does not exist, it will be created. +does not exist, a new volume group will be created. The default attributes +for the new volume group can be specified with \fB\-\-alloc\fR, +\fB\-\-clustered\fR, \fB\-\-maxlogicalvolumes\fR, \fB\-\-metadatatype\fR, +\fB\-\-maxphysicalvolumes\fR, and \fB\-\-physicalextentsize\fR +(see \fBvgcreate(8)\fR for a description of these options). +If any of these options are not given, the default attribute(s) are taken +from +.I SourceVolumeGroupName\fP. + +If +.I DestinationVolumeGroupName +does exist, it will be checked for compatibility with +.I SourceVolumeGroupName +before the physical volumes are moved. + 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.
reply other threads:[~2008-01-17 3:18 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=20080117031818.30750.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).