From: Lance Reed <lreed@ruckusnetwork.com>
To: Linux-LVM@Sistina.com
Subject: [linux-lvm] will pvcreate destroy lvm data on an already exsiting PV
Date: Sat, 30 Apr 2005 15:31:01 -0400 [thread overview]
Message-ID: <4273DCF5.3030905@ruckusnetwork.com> (raw)
I know you guys don't normally respond to direct email about LVM.
But I have a situation that the PV in a VG seems to have lost its
metadata, and
there is a discrepancy between What the OS thinks the partition for a
device that uses
LVM is and what LVM thinks it should be (/dev/sde vs /dev/sde1). A
vgrestore complains
about pv_read not working. So my question is, if I run a new pvcreate
on the disk device,
will it destroy the LVM data on the existing device. Or will it just
setup a placeholder for
the metadata, and I can then just do a vgcgrestore and put that back in
place without
losing data.
Thanks for any suggestions and your time.
Sincerely,
Lance Reed
lreed@ruckusnetwork.com
next reply other threads:[~2005-04-30 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 19:31 Lance Reed [this message]
2005-05-03 13:59 ` [linux-lvm] will pvcreate destroy lvm data on an already exsiting PV David Mohr
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=4273DCF5.3030905@ruckusnetwork.com \
--to=lreed@ruckusnetwork.com \
--cc=Linux-LVM@Sistina.com \
--cc=linux-lvm@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.