All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Kerndler <h.kerndler@jusline.com>
To: linux-lvm@sistina.com
Subject: Re: [Fwd: [linux-lvm] LVM export]
Date: Wed, 09 May 2001 05:11:21 +0200	[thread overview]
Message-ID: <3AF8B558.CBAB57EB@jusline.com> (raw)
In-Reply-To: 3AF6A532.38B30041@lanzenberg.at

We have found the command vgcfgrestore and we have him tested.
We have follow command used: vgcfgrestore -n vol0 /dev/hda4 and then comes this
error:
vgcfgrestore -- ERROR "pv_read(): PV exported" reading physical volume "/dev/hda4"

Is the VG demaged ?

>
>
>   ------------------------------------------------------------------------
>
> Subject: Re: [linux-lvm] LVM export
> Date: Mon, 7 May 2001 13:58:47 +0200
> From: Torsten Landschoff <torsten@pclab.ifg.uni-kiel.de>
> Reply-To: linux-lvm@sistina.com
> To: linux-lvm@sistina.com
> References: <3AF68126.93ACCE81@lanzenberg.at> <20010507134024.A26477@sistina.com>
>
> On Mon, May 07, 2001 at 01:40:24PM +0000, Heinz J. Mauelshagen wrote:
>
> > There's a hack to reactivate it in case you still have a valid VGDA backup,
> > but let me first understand what your actual problem is, before we can decide
> > to try that.
>
> I guess he tried to move a disk to a new one by exporting the volume
> group, moving the data onto the new disk and importing that one. I guess
> the solution would be to import the volume group from the old disk
> (assuming the data is still available on it) and using pvcreate,
> vgextend and pvmove to get the data on the new disk, the use vgreduce
> to remove the pv of the old disk and remove it from the system.
>
> Greetings
>
>         Torsten
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
>
>   ------------------------------------------------------------------------
>
> Subject: Re: [linux-lvm] LVM export
> Date: Mon, 7 May 2001 13:40:24 +0000
> From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
> Reply-To: linux-lvm@sistina.com
> To: linux-lvm@sistina.com
> References: <3AF68126.93ACCE81@lanzenberg.at>
>
> On Mon, May 07, 2001 at 01:04:06PM +0200, h.kerndler@lanzenberg.at wrote:
> > Hello !
> > Yesterday, I have tested the export/import Funktion from LVM.
> > I have exported the LVM, that has gone.
>
> Without further information, I can't provide a solution.
>
> Do you mean you successfully run "vgexport VGName" on your deactivated VG
> named "VGName"?
>
> > In the next step I would import the LVM on a other disk.
>
> What do you mean with "other disk"?
>
> The vgimport(8) command has the synopsis:
>
>    vgimport VGName PhysicalVolumePath [PhysicalVolumePath...]
>
> If you exported the VG just to test the feature as you mentioned,
> you should run pvscan which should list you all of the physical volume
> pathes belonging to the exported VG and feed those pathes into vgimport.
>
> See "man vgimport" for further details.
>
> > The LVM has not imported the LVM on a other disc, becaus I became a
> > Failure.
>
> What was the failure message?
>
> > My question, can I make a un-export on the old-disk?
>
> No, you can just import it.
>
> There's a hack to reactivate it in case you still have a valid VGDA backup,
> but let me first understand what your actual problem is, before we can decide
> to try that.
>
> >
> > Thanks, Harald
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
>
> --
>
> Regards,
> Heinz    -- The LVM Guy --
>
> *** Software bugs are stupid.
>     Nevertheless it needs not so stupid people to solve them ***
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> Heinz Mauelshagen                                 Sistina Software Inc.
> Senior Consultant/Developer                       Am Sonnenhang 11
>                                                   56242 Marienrachdorf
>                                                   Germany
> Mauelshagen@Sistina.com                           +49 2626 141200
>                                                        FAX 924446
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

--
mit freundlichen Gr��en
J�rgen Greil

JUSLINE - Direkt zu Ihrem Recht
http://www.jusline.com
e-mail: dev5@jusline.com

       reply	other threads:[~2001-05-09  3:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AF6A532.38B30041@lanzenberg.at>
2001-05-09  3:11 ` Harald Kerndler [this message]
2001-05-09  9:22   ` [Fwd: [linux-lvm] LVM export] Heinz J. Mauelshagen

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=3AF8B558.CBAB57EB@jusline.com \
    --to=h.kerndler@jusline.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.