linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Misc Things <formisc@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Installation fails if VG is exported
Date: Tue, 7 Jun 2011 10:53:02 -0400	[thread overview]
Message-ID: <BANLkTikGwknQ7r5P76UqifeCeFRkaX=G=g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1106070822200.11302@bmsred.bmsi.com>

On Tue, Jun 7, 2011 at 8:25 AM, Stuart D. Gathman <stuart@bmsi.com> wrote:
> On Mon, 6 Jun 2011, Misc Things wrote:
>
>> During the HDs checking phase, anaconda terminates with the message "
>> unalbe to activate exported VG".
>> I googled around with not much success. The only similar issue was
>> closed in2007 (https://bugzilla.redhat.com/show_bug.cgi?id=191879)
>
> Exporting the VG is *supposed* to prevent activation. �You can reverse this
> with vgimport. �Why did you wish to prevent activation? �Normally,
> vgexport is used prior to physically removing a VG from the system.
> (And then vgimport after attaching the drives to the new system.)

Well, I just want to keep my data intact while i'm playing with the
installation. I understand that @ this point it's just easier to pull
the power on the HDs with the VG in question. But i'm curious why this
is a problem...

Andrew

  reply	other threads:[~2011-06-07 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  2:29 [linux-lvm] Installation fails if VG is exported Misc Things
2011-06-07 12:25 ` Stuart D. Gathman
2011-06-07 14:53   ` Misc Things [this message]
2011-06-07 15:25     ` Stuart D. Gathman
2011-06-07 15:38       ` Stuart D. Gathman
2011-06-07 17:01         ` Misc Things
2011-06-13 15:05         ` Andrew Z

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='BANLkTikGwknQ7r5P76UqifeCeFRkaX=G=g@mail.gmail.com' \
    --to=formisc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).