All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 3/2] document --norestorefile in pvcreate man page
Date: Wed, 11 Aug 2010 17:07:57 -0400	[thread overview]
Message-ID: <20100811210756.GA8422@redhat.com> (raw)
In-Reply-To: <1281479088-1553-1-git-send-email-snitzer@redhat.com>

document --norestorefile in pvcreate man page

Signed-off-by: Mike Snitzer <snitzer@redhat.com>
---
 man/pvcreate.8.in |    9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

Index: lvm2/man/pvcreate.8.in
===================================================================
--- lvm2.orig/man/pvcreate.8.in
+++ lvm2/man/pvcreate.8.in
@@ -17,6 +17,7 @@ pvcreate \- initialize a disk or partiti
 .RB [ \-\-dataalignment alignment ]
 .RB [ \-\-dataalignmentoffset alignment_offset ]
 .RB [ \-\-restorefile file ]
+.RB [ \-\-norestorefile ]
 .RB [ \-\-setphysicalvolumesize size ]
 .RB [ \-u | \-\-uuid uuid ]
 .RB [ \-\-version ]
@@ -60,7 +61,9 @@ Specify the uuid for the device.  
 Without this option, \fBpvcreate\fP generates a random uuid.
 All of your physical volumes must have unique uuids.
 You need to use this option before restoring a backup of LVM metadata 
-onto a replacement device - see \fBvgcfgrestore\fP(8).
+onto a replacement device - see \fBvgcfgrestore\fP(8).  As such, use of
+\fB--restorefile\fP is compulsory unless the \fB--norestorefile\fP is
+used.
 .TP
 .BR \-y ", " \-\-yes
 Answer yes to all questions.
@@ -138,6 +141,10 @@ the same place and not get overwritten b
 a mechanism to upgrade the metadata format or to add/remove metadata
 areas. Use with care. See also \fBvgconvert\fP(8).
 .TP
+.BR \-\-norestorefile
+In conjunction with \fB--uuid\fP, this allows a uuid to be specified
+without also requiring that a backup of the metadata be provided.
+.TP
 .BR \-\-labelsector " sector"
 By default the PV is labelled with an LVM2 identifier in its second 
 sector (sector 1).  This lets you use a different sector near the



      parent reply	other threads:[~2010-08-11 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 22:24 [PATCH 1/2] require --restorefile when using pvcreate --uuid Mike Snitzer
2010-08-10 22:24 ` [PATCH v3 2/2] change default alignment of pe_start to 1MB Mike Snitzer
2010-08-11 21:25   ` [PATCH v4 " Mike Snitzer
2010-08-11 21:43     ` [PATCH v5 " Mike Snitzer
2010-08-11 23:44       ` [PATCH v6 " Mike Snitzer
2010-08-11 21:07 ` Mike Snitzer [this message]

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=20100811210756.GA8422@redhat.com \
    --to=snitzer@redhat.com \
    --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.