All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] PV Status NOT available
Date: Mon Feb 10 07:38:01 2003	[thread overview]
Message-ID: <20030210143353.A5958@sistina.com> (raw)
In-Reply-To: <000801c2d0e8$91e8d320$0d01a8c0@aphrodite>; from rupert.hair@ntlworld.com on Mon, Feb 10, 2003 at 09:41:18AM -0000

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

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-02-10  7:38 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 [this message]
2003-02-10  8:02   ` Patrick Boutilier
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=20030210143353.A5958@sistina.com \
    --to=mauelshagen@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.