Linux LVM users
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] My VG is gone...
Date: Fri, 31 Aug 2001 10:22:06 +0100	[thread overview]
Message-ID: <20010831102206.A391@btconnect.com> (raw)
In-Reply-To: <20010831071518.07f51602.rasmus.wiman@sami.se>; from rasmus.wiman@sami.se on Fri, Aug 31, 2001 at 07:15:18AM +0200

On Fri, Aug 31, 2001 at 07:15:18AM +0200, Rasmus Wiman wrote:
> ...And I want them up quickly!
> 
> This evening I added a 36 GB drive to our department server. I did a
> vgextend on it and somehow it all went terribly wrong. It seems to me that
> the new drive got added twice, but with different UUIDs. Of course there
> is no way vgchange will bring it online. Is there a solution to the
> problem? I downloaded LDE from <http://lde.sourceforge.net/> to have a
> look at it, but I don't know what to alter. I run Slackware 8 with Kernel
> 2.4.8 and LVM-1.0. The attached files contain output from pvdata -U -V -PP
> on all three partitions.

You're right sdb1 appears to have been added twice with seperate
UUID's.  I'm at a loss to explain this at the moment.  Did you run
pvcreate more than once on sdb1 ? (I want to know where that extra
uuid came from).

- Joe

  parent reply	other threads:[~2001-08-31  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  5:15 [linux-lvm] My VG is gone Rasmus Wiman
2001-08-31  7:41 ` Rasmus Wiman
2001-08-31  9:22 ` Joe Thornber [this message]
2001-09-02 18:07   ` Rasmus Wiman
2001-09-02 19:03     ` svetljo
2001-09-04 12:43     ` AJ Lewis
  -- strict thread matches above, loose matches on Subject: below --
2001-09-04 20:51 Diehl, Jeffrey
2001-09-05  8:04 ` Rasmus Wiman
2001-09-05 18:56 Diehl, Jeffrey
2001-09-05 20:41 ` AJ Lewis
2001-09-06 16:36 Diehl, Jeffrey

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=20010831102206.A391@btconnect.com \
    --to=thornber@btconnect.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox