From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM don't work anymore (wrong version?)
Date: Thu, 15 Feb 2001 13:03:03 -0700 (MST) [thread overview]
Message-ID: <200102152003.f1FK35J30665@webber.adilger.net> (raw)
In-Reply-To: <B45465FD9C23D21193E90000F8D0F3DF683960@mailsrv.linkvest.ch> from Jean-Eric Cuendet at "Feb 15, 2001 11:21:24 am"
Jean-Eric Cuendet writes:
> I have this same problem on two of our servers! The 2 runs the same kernel:
> 2.4.1 with ACL patch and LVM 0.9.1beta4
>
> [root@zorro /root]# pvscan -u
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE PV "/dev/md6" with UUID
> "v7Y8gz-KMXB-d6Iq-Y0U1-iiSo-javD-wOL89P" is associated to an
> unknown VG (run vgscan)
> pvscan -- ACTIVE PV "/dev/md7" with UUID
> "xTl7Nc-6DhQ-KV3c-HHd0-LI50-nQwq-wFBYCG" is associated to an
> unknown VG (run vgscan)
> pvscan -- ACTIVE PV "/dev/md8" with UUID
> "oDXPq6-s9Zn-dOHF-ss8J-Rdxt-jTKT-wFoIGQ" is associated to an
> unknown VG (run vgscan)
Try running 'pvdata -U' on each of the PV's, and see if there are empty
UUID slots on some of them. This is a bug with the old LVM tools. If
this is true, you can try to comment out the section in pv_read_all_pv_of_vg
which verifies the UUIDs (starts like "if (uuids) {"), and try vgscan
again.
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-02-15 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 10:21 [linux-lvm] LVM don't work anymore (wrong version?) Jean-Eric Cuendet
2001-02-15 20:03 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 7:41 Jean-Eric Cuendet
2001-02-16 17:11 ` Andreas Dilger
2001-02-14 16:45 Jean-Eric Cuendet
2001-02-14 17:56 ` Heinz J. Mauelshagen
2001-02-14 10:15 Jean-Eric Cuendet
2001-02-14 17:26 ` 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=200102152003.f1FK35J30665@webber.adilger.net \
--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).