From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM don't work anymore (wrong version?)
Date: Fri, 16 Feb 2001 10:11:33 -0700 (MST) [thread overview]
Message-ID: <200102161711.f1GHBX014742@webber.adilger.net> (raw)
In-Reply-To: <B45465FD9C23D21193E90000F8D0F3DF683970@mailsrv.linkvest.ch> from Jean-Eric Cuendet at "Feb 16, 2001 08:41:53 am"
Jean-Eric writes:
> > 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
>
> I have 13 slots and the 13th is EMPTY. Is that what you mean?
Yes. This was a bug in the old (0.9.1beta2?) LVM user tools. The problem is
that this data was written to disk incorrectly, and now vgscan doesn't work.
> > 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.
>
> I did it and vgscan output nothing about Volume Groups!
> Output of debug vgscan is attached.
I don't see any attachment. I was looking at the pv_read_all_pv_of_vg()
code, and the section actually starts "if (uuids > 0) {", so you can
replace this with "if (0) {" and the UUID checking will be skipped.
This _should_ fix your problem, but it is possible there is also another
problem as well.
> Here is the output of a vgchange:
> [root@fatboy 0.9.1_beta4]# echo -ne "NOTSURE_HDX\0" > /etc/lvmtab
> [root@fatboy 0.9.1_beta4]# vgchange -ay
> vgchange -- ERROR: physical volume "/dev/hdc9" of volume group "NOTSURE_HDX"
> is inconsistent
> vgchange -- run vgscan
>
> FYI, I have hda1, hda5->hda10 + hdc1, hdc5->hdc10 in the VG NOTSURE_HDX.
> hdc9 seems broken, but why? And how to restore?
You can try restoring your VGDA with "vgcfgrestore /dev/hdc9". You may
have to restore the VGDA on all of the disks at the same time, I'm not
sure. The good news is that if you do a vgcfgrestore with the new (beta4)
tools it will also fix the UUID problem above.
Cheers, Andreas
PS - it is strange that you have multiple partitions on the same disk as
separate PVs. It is the most efficient (space wise) to only make a
single large PV on each disk.
--
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-16 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 7:41 [linux-lvm] LVM don't work anymore (wrong version?) Jean-Eric Cuendet
2001-02-16 17:11 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-15 10:21 Jean-Eric Cuendet
2001-02-15 20:03 ` 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=200102161711.f1GHBX014742@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).