All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] PV Status NOT available
Date: Tue Feb 11 10:44:01 2003	[thread overview]
Message-ID: <3E4927E0.5040502@ednet.ns.ca> (raw)
In-Reply-To: <20030211163014.C10750@sistina.com>

Works for me.

Old pvdisplay:


--- 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





Patched pvdisplay:


--- 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             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







Heinz J . Mauelshagen wrote:
> On Mon, Feb 10, 2003 at 03:33:44PM -0000, Rupert Hair wrote:
> 
>>>do all 3 PVs show up active (the [] following 'PV:' should contain 'AA'
>>>unless you set a PV to inallocatable) in /proc/lvm/global ?
>>
>>LVM driver LVM version 1.0.5(15/07/2002)
>>
>>Total:  1 VG  3 PVs  1 LV (1 LV open 1 times)
>>
>>Global: 179278 bytes malloced   IOP version: 10   5 days 1:33:43 active
>>
>>VG:  datavg  [3 PV, 1 LV/1 open]  PE Size: 32768 KB
>>  Usage [KB/PE]: 357171200 /10900 total  357171200 /10900 used  0 /0 free
>>  PVs: [AA] hdg1                  119996416 /3662    119996416 /3662
>>0 /0
>>       [AA] hde1                  119996416 /3662    119996416 /3662
>>0 /0
>>       [AA] hdf1                  117178368 /3576    117178368 /3576
>>0 /0
>>    LV:  [AWDL  ] datalv                   357171200 /10900    1x open
>>
>>Looks like Patrick and I have the same problem.  Thanks for your help Heinz.
> 
> 
> Hmmm, pretty od really. pvdisplay calls the pv_status() lib function
> which retrieves the information from the kernel. That's why i asked for
> the proc output which shows that the PVs are _active_ and allocatable.
> 
> Wait, need to preserve the core flags to make this work...
> 
> Could you test if the following patch to pvdisplay.c helps ?
> 
> diff -u -B -u -r1.25 pvdisplay.c
> --- tools/pvdisplay.c   6 Feb 2003 15:05:30 -0000       1.25
> +++ tools/pvdisplay.c   11 Feb 2003 15:31:51 -0000
> @@ -42,6 +42,7 @@
>   *    06/02/2002 - cope with changed pv_get_size() return cast
>   *    07/02/2002 - fixes for > 1TB support
>   *    17/02/2002 - avoid pv_get_size() altogether
> + *    11/02/2002 - fixed bug preventing correct 'active' status displayed [HM]
>   *
>   */
> 
> @@ -231,7 +232,8 @@
>           return LVM_EPVDISPLAY_PV_CHECK_CONSISTENCY;
>        }
> 
> -      /* restore the from disk pointer */
> +      /* restore the from disk pointer _but_ preserve kernel status */
> +      pv_from_disk->pv_status = pv->pv_status;
>        pv = pv_from_disk;
> 
>        if ( opt_c == 0) {
> 
> 
> 
>>Rupert
>>
>>
>>
>>_______________________________________________
>>linux-lvm mailing list
>>linux-lvm@sistina.com
>>http://lists.sistina.com/mailman/listinfo/linux-lvm
>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
> 
> 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2003-02-11 10:44 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
2003-02-10  9:31   ` Rupert Hair
2003-02-11  9:34     ` Heinz J . Mauelshagen
2003-02-11 10:44       ` Patrick Boutilier [this message]
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=3E4927E0.5040502@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 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.