From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan won't recognize my VG
Date: Mon, 19 Mar 2001 13:37:26 -0700 (MST) [thread overview]
Message-ID: <200103192037.f2JKbQn17560@webber.adilger.int> (raw)
In-Reply-To: <3AB6687F.EBC538E0@in.tum.de> from David Vidal Rodriguez at "Mar 19, 2001 09:13:51 pm"
David Vidal R. (vidalrod@in.tum.de) writes:
> Linux-version: 2.4.0
> LVM-version: 0.9 (IO-Protocoll 10) -- the version of the Linus stock
> kernel, ie, no patches applied.
What version of user tools do you have? You should use the beta6 tools.
> pvscan detects all my PVs and adds that they belong to "an unknown VG
> (run vgscan)."
>
> I runned pvdata -U (get UUIDs) and I got some interesting information
> about my PVs. For simplicity's sake I'll use identifiers for the UUIDs.
>
> List of UUIDs:
>
> part5:
> <uuid1>
> <uuid2>
>
> part7:
> <uuid3>
> <uuid2>
>
> part2:
> <uuid2>
> <uuid2>
Your UUIDs are broken. This is why vgscan is failing. All of them are
incorrect. Each should list all 3 UUIDs on each disk. There was a bug
in the user tools related to this, fixed in beta4 (I think). It is
definitely fixed in beta 6.
> it would be very frustrating to lose 3.2 Gb of data that isn't messed up...
Yes, your data is still on the disk, but it would be safer if you had a
backup.
> Please tell me if you need more information in order to find out what's
> gone wrong.
If you have the new beta6 tools, but an old beta2 kernel, you need to
apply a patch to vg_create_restore.c (I posted it to lvm-devel a week
ago or so), for vgscan to work properly. If you run vgcfgrestore with
the beta6 tools, it should write the UUIDs to disk properly.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-19 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger [this message]
2001-03-20 18:52 ` David Vidal Rodriguez
2001-03-20 19:17 ` AJ Lewis
2001-03-20 19:25 ` Andreas Dilger
2001-03-20 19:35 ` David Vidal Rodriguez
2001-03-20 20:00 ` David Vidal Rodriguez
2001-03-20 20:21 ` Andreas Dilger
2001-03-20 20:36 ` David Vidal Rodriguez
2001-03-21 0:29 ` Kirth
2001-03-21 18:30 ` David Vidal Rodriguez
2001-03-21 19:17 ` Andreas Dilger
2001-03-23 14:55 ` David Vidal Rodriguez
2001-03-23 22:36 ` Andreas Dilger
2001-03-20 20:57 ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33 ` Lars Kellogg-Stedman
2001-03-22 23:59 ` Anders Widman
[not found] ` <0103262137020G.01456@lyta>
2001-03-27 21:48 ` Anders Widman
2001-03-27 21:56 ` Ragnar Kjørstad
2001-03-27 22:29 ` Anders Widman
2001-03-27 22:45 ` Ragnar Kjørstad
2001-03-28 6:43 ` Russell Coker
2001-03-31 17:17 ` Anders Widman
2001-03-20 20:23 ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31 ` AJ Lewis
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=200103192037.f2JKbQn17560@webber.adilger.int \
--to=adilger@turbolinux.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;
as well as URLs for NNTP newsgroup(s).