From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] PV Status NOT available
Date: Mon Feb 10 08:02:01 2003 [thread overview]
Message-ID: <3E47B064.9040506@ednet.ns.ca> (raw)
In-Reply-To: <20030210143353.A5958@sistina.com>
I have the same problem on RedHat 8.0
# pvdisplay /dev/sda6
--- Physical volume ---
PV Name /dev/sda6
VG Name imap_vg
PV Size 261.11 GB [547591527 secs] / NOT usable 16.25 MB
[LVM: 189 KB]
PV# 1
PV Status NOT available
Allocatable yes (but full)
Cur LV 1
PE Size (KByte) 16384
Total PE 16710
Free PE 0
Allocated PE 16710
PV UUID O7WnwM-5ASt-AsiV-8BlZ-h6KP-NjFl-cdY33C
# cat /proc/lvm/global
LVM driver LVM version 1.0.6(25/10/2002)
Total: 1 VG 1 PV 1 LV (1 LV open 1 times)
Global: 271038 bytes malloced IOP version: 10 63 days 17:26:47 active
VG: imap_vg [1 PV, 1 LV/1 open] PE Size: 16384 KB
Usage [KB/PE]: 273776640 /16710 total 273776640 /16710 used 0 /0 free
PV: [AA] sda6 273776640 /16710 273776640 /16710
0 /0
LV: [AWDL ] imap_lv 273776640 /16710 1x open
Heinz J . Mauelshagen wrote:
> Rupert,
>
> do all 3 PVs show up active (the [] following 'PV:' should contain 'AA'
> unless you set a PV to inallocatable) in /proc/lvm/global ?
>
> if so pvdisplay (pv_status in the library respectively) doesn't seem
> to get the PV_ACTIVE status from the kernel correctly.
>
>
> On Mon, Feb 10, 2003 at 09:41:18AM -0000, Rupert Hair wrote:
>
>>Hi Everyone.
>>
>>I have a rather strange 'problem' with my LVM setup. I am using a very
>>standard install of Redhat 8.0 (Kernel 2.4.18-14smp (I guess the "-14smp" is
>>some Redhat version number.)) with LVM version 1.0.3(19/02/2002). I used
>>the Redhat installer to create a single VG (datavg) and LV (datalv) made up
>>of 3 PVs (hdd5 hdd6 hdd7 (Yes all three PVs are on the same disk as this is
>>just a test setup.)). This all went fine and the installer created an ext3
>>filesystem on top of the LV. I have put some data on the filesystem and
>>rebooted a few times to test it out and everything works great.
>>
>>Now the 'problem': two of my PVs (hdd5 hdd7) have a status of "NOT
>>available" (reported by pvdisplay). This is very strange as the whole setup
>>seems to work fine and all three PVs are on the same disk (which is working
>>fine). I have attached various files which are the outputs of some of the
>>LVM utilities that seemed useful.
>>
>>I would be very grateful if anyone could shed any light on this problem and
>>what I have done wrong.
>>
>>Thanks.
>>Rupert
>
>
next prev parent reply other threads:[~2003-02-10 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 6:27 [linux-lvm] PV Status NOT available Rupert Hair
2003-02-10 7:38 ` Heinz J . Mauelshagen
2003-02-10 8:02 ` Patrick Boutilier [this message]
2003-02-10 9:31 ` Rupert Hair
2003-02-11 9:34 ` Heinz J . Mauelshagen
2003-02-11 10:44 ` Patrick Boutilier
2003-02-11 16:47 ` Rupert Hair
2003-02-13 6:09 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 8:09 Gunther Clasen
2006-02-22 15:01 Gunther Clasen
2002-12-09 8:03 [linux-lvm] PV Status: " Patrick Boutilier
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=3E47B064.9040506@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--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).