From: Thomas Bader <thomas@t-bader.ch>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LV not available
Date: Fri Dec 27 07:56:02 2002 [thread overview]
Message-ID: <20021227135657.GB13292@trash.net> (raw)
I've got Linux 2.4.20 patched with LVM 1.0.6 up and running.
During a power outage, my system rebooted and my volume
group didn't came up.
One of the PVs in this VG shows like this:
-->-->-->--
fullmoon:~# pvdisplay /dev/md/4
--- Physical volume ---
PV Name /dev/md/4
VG Name vg00
PV Size 57.81 GB [121242368 secs] / NOT usable 16.18 MB [LVM: 138 KB]
PV# 3
PV Status NOT available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 16384
Total PE 3699
Free PE 0
Allocated PE 3699
PV UUID nyoJQM-GYcF-wzWK-H80y-5bgs-UHIs-VhINj6
--<--<--<--
How can its status changed back to available? All other PVs
in this VG have status == available.
When I'm running vgscan and vgchange -a y my volume group
cannot be found:
-->-->-->--
fullmoon:~# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- ERROR "pv_read_all_pv_of_vg(): PV number" can't get data of volume group "vg00" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume group
fullmoon:~# vgchange -a y
vgchange -- no volume groups found
fullmoon:~#
--<--<--<--
Any hints about how to fix this?
--
<https://trash.net/~thomasb/> PGP and OpenPGP encrypted mail preferred.
"We can't buy more time, 'cause time won't accept our money."
-- Bad Religion
next reply other threads:[~2002-12-27 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 7:56 Thomas Bader [this message]
2002-12-27 15:12 ` [linux-lvm] LV not available Donald Thompson
2002-12-27 15:27 ` Thomas Bader
2002-12-27 16:17 ` Thomas Bader
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=20021227135657.GB13292@trash.net \
--to=thomas@t-bader.ch \
--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