All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgcfgrestore ouput
Date: Mon Oct 21 02:18:01 2002	[thread overview]
Message-ID: <20021021071750.GA838@tykepenguin.com> (raw)
In-Reply-To: <1035163216.1245.4.camel@localhost.localdomain>

On Sun, Oct 20, 2002 at 08:20:16PM -0500, Austin Gonyou wrote:
> 
> I tarred up the /etc/lvm* stuff from one box that has a similar
> configuration (two whole disks, /dev/sdb and /dev/sdc, in one vg), and
> then put it on my target host and attempted to restore the
> configuration. 
> 
> Below is the output I get. I guess, all I need to know right now, is are
> the first 512 bytes of each disk all that is used for the pv
> information, or is it more than that? 
> 
> Also, can pvcreate be used without destroying the underlying
> filesystems? TIA!!!
> 
> <vgcfgrestore>
> [root@localhost root]# vgcfgrestore -n data /dev/sdb
> vgcfgrestore -- INFO: using backup file "/etc/lvmconf/data.conf"
> vgcfgrestore -- ERROR "pv_read(): PV identifier invalid" reading
> physical volume "/dev/sdb"
> 
> [root@localhost root]# vgcfgrestore -n data /dev/sdc
> vgcfgrestore -- INFO: using backup file "/etc/lvmconf/data.conf"
> vgcfgrestore -- ERROR "pv_read(): PV identifier invalid" reading
> physical volume "/dev/sdc"
> </vgcfgrestore>
> 

It'll be fine :-) just

# pvcreate /dev/sdb
# pvcreate /dev/sdc

and then issue the vgcfgrestore commands you have above.

then 

vgscan && vgchange -ay
-- 

patrick

  reply	other threads:[~2002-10-21  2:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20 20:20 [linux-lvm] vgcfgrestore ouput Austin Gonyou
2002-10-21  2:18 ` Patrick Caulfield [this message]
2002-10-21  2:59   ` Austin Gonyou
2002-10-21  3:12     ` Patrick Caulfield

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=20021021071750.GA838@tykepenguin.com \
    --to=caulfield@sistina.com \
    --cc=linux-lvm@sistina.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.