All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine <lists@chwing.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vg works fine under FC3, but not FC4
Date: Thu, 18 Aug 2005 12:07:59 +0200	[thread overview]
Message-ID: <43045DFF.1050105@chwing.com> (raw)
In-Reply-To: <20050816194210.GO29587@agk.surrey.redhat.com>

from my experience, this doesn't help, it seems that pvscan, vgscan 
doesn't recognize whole device as lvm capable device and then remove it 
from .cache (so your vg seems to disappear but if you manually put your 
device in .cache, it fixes everything)


see output for exemple :
pitch:/etc/lvm# pvs
  PV         VG   Fmt  Attr PSize   PFree
  /dev/hdc   vg0  lvm2 a-    19.11G 19.11G
  /dev/hdd   vg0  lvm2 a-   149.05G  4.05G
pitch:/etc/lvm#
pitch:/etc/lvm#
pitch:/etc/lvm# pvscan
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  PV unknown device   VG vg0   lvm2 [149.05 GB / 4.05 GB free]
  PV /dev/hdc         VG vg0   lvm2 [19.11 GB / 19.11 GB free]
  Total: 2 [168.16 GB] / in use: 2 [168.16 GB] / in no VG: 0 [0   ]
pitch:/etc/lvm# pvs
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  Couldn't find all physical volumes for volume group vg0.
  Can't read vg0: skipping
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  Couldn't find all physical volumes for volume group vg0.
  Can't read vg0: skipping

note that it doesn't happen on both disks, but they were set up identically.

see also this output, pvdisplay on the faulty device seems to fix it :
pitch:/etc/lvm# vgdisplay
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  Couldn't find all physical volumes for volume group vg0.
  Volume group "vg0" doesn't exist
pitch:/etc/lvm# pvdisplay
  Couldn't find device with uuid 'iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs'.
  --- Physical volume ---
  PV Name               unknown device
  VG Name               vg0
  PV Size               149.05 GB / not usable 0  
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              38156
  Free PE               1036
  Allocated PE          37120
  PV UUID               iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs
  
  --- Physical volume ---
  PV Name               /dev/hdc
  VG Name               vg0
  PV Size               19.11 GB / not usable 0  
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              4892
  Free PE               4892
  Allocated PE          0
  PV UUID               vzCHIG-WqYt-w2Kv-qGog-vK74-GEBu-svsWBm
  
pitch:/etc/lvm# pvdisplay /dev/hdd
  --- Physical volume ---
  PV Name               /dev/hdd
  VG Name               vg0
  PV Size               149.05 GB / not usable 0  
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              38156
  Free PE               1036
  Allocated PE          37120
  PV UUID               iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs
  

pitch:/etc/lvm#
pitch:/etc/lvm# pvdisplay
  --- Physical volume ---
  PV Name               /dev/hdd
  VG Name               vg0
  PV Size               149.05 GB / not usable 0  
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              38156
  Free PE               1036
  Allocated PE          37120
  PV UUID               iZzizb-LmBD-0wx1-QD3g-76aO-1zJI-d61tNs
  
  --- Physical volume ---
  PV Name               /dev/hdc
  VG Name               vg0
  PV Size               19.11 GB / not usable 0  
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              4892
  Free PE               4892
  Allocated PE          0
  PV UUID               vzCHIG-WqYt-w2Kv-qGog-vK74-GEBu-svsWBm
  
pitch:/etc/lvm# vgs
  VG   #PV #LV #SN Attr  VSize   VFree
  vg0    2   1   0 wz--n 168.16G 23.16G

so for me at least, the best practice for now is to set a partition on 
the whole disk (hdd1) set its type '8e' and use it instead of the whole 
device. I didnt have any problem working like this.

fyi: debian sarge with :
pitch:~# vgscan --version
  LVM version:     2.01.04 (2005-02-09)
  Library version: 1.01.00-ioctl (2005-01-17)
  Driver version:  4.1.1

Alasdair G Kergon wrote:

>No - I'm suggesting you need to check if any *whole device* PVs like hdd 
>actually have partition tables on them, and if so, remove them.
>
>Alasdair
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@redhat.com
>https://www.redhat.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>  
>

  parent reply	other threads:[~2005-08-18 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16  7:26 [linux-lvm] vg works fine under FC3, but not FC4 john_gore
2005-08-16 12:54 ` Richard Ray
2005-08-16 18:58   ` john_gore
2005-08-16 19:19     ` Richard Ray
2005-08-16 19:04 ` Alasdair G Kergon
2005-08-16 19:40   ` john_gore
2005-08-16 19:42     ` Alasdair G Kergon
2005-08-16 23:09       ` john_gore
2005-08-18 10:07       ` Antoine [this message]
2005-08-19 19:04         ` john_gore

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=43045DFF.1050105@chwing.com \
    --to=lists@chwing.com \
    --cc=linux-lvm@redhat.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.