From: David Mohr <squisher@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] will pvcreate destroy lvm data on an already exsiting PV
Date: Tue, 3 May 2005 08:59:55 -0500 [thread overview]
Message-ID: <472d4b25050503065924417838@mail.gmail.com> (raw)
In-Reply-To: <4273DCF5.3030905@ruckusnetwork.com>
I'm just a listener on this list and by no means an expert on this:
should my memory not fail me, then pvcreate on an existing PV should
be safe to run. I think the reason why noone answers you is because
you really should read through the archive and probably some howto's,
I'm pretty sure I've seen this question a couple of times on this
list. Noone likes to give answers that have already been given a
couple of times.
~David
On 4/30/05, Lance Reed <lreed@ruckusnetwork.com> wrote:
> 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
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
prev parent reply other threads:[~2005-05-03 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 19:31 [linux-lvm] will pvcreate destroy lvm data on an already exsiting PV Lance Reed
2005-05-03 13:59 ` David Mohr [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=472d4b25050503065924417838@mail.gmail.com \
--to=squisher@gmail.com \
--cc=david@mcbf.net \
--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.