linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM and Device Mapper
Date: Sat, 17 Jun 2006 02:42:34 +0200	[thread overview]
Message-ID: <20060617004234.GB31760@percy.comedia.it> (raw)
In-Reply-To: <4492CC31.9060909@fastenal.com>

On Fri, Jun 16, 2006 at 10:20:17AM -0500, Kelly Sauke wrote:
>C'est Pierre wrote:
>> That kinda worked out. I tried your example as-is, and it still shows
>> 'Found duplicate PV' messages and additionally it said "vg sucessfully
>> created" but in fact, when I issue a vgdisplay, it doesn't show the vg
>> created.
>> 
>
>Try excluding all of your sd paths in the filter line.  If you look at my
>example, it seems my local disk /dev/sda2, my mpath devices and then it hides
>everything else.  Thats how I got the 'Found duplicate PV' errors to go away.
>
>After setting that, run an lvmdiskscan to verify that its seeing your multipath
>devices and excuding the sd devices.

yes, please edit your filter line, so it will ignore the /dev/sd*
devices
>
....
>>  (erased the other VG)
>>  --- Volume group ---
>>  VG Name               clusterfs
>>  System ID
>>  Format                lvm2
>>  Metadata Areas        1
>>  Metadata Sequence No  2
>>  VG Access             read/write
>>  VG Status             resizable
>>  MAX LV                0
>>  Cur LV                1
>>  Open LV               0
>>  Max PV                0
>>  Cur PV                1
>>  Act PV                1
>>  VG Size               50.00 GB
>>  PE Size               4.00 MB
>>  Total PE              12799
>>  Alloc PE / Size       25 / 100.00 MB
>>  Free  PE / Size       12774 / 49.90 GB
>>  VG UUID               QxEuzf-SJMU-mmlo-c4mr-6SLs-AU6X-X8A6Fi
>> 
>> 
>> # lvdisplay
>>  (skipped the others)
>>  --- Logical volume ---
>>  LV Name                /dev/clusterfs/ora1
>>  VG Name                clusterfs
>>  LV UUID                hAt2Tx-Tf2U-oD10-3W77-sIo6-Q3nf-5fG3AT
>>  LV Write Access        read/write
>>  LV Status              available
>>  # open                 0
>>  LV Size                100.00 MB
>>  Current LE             25
>>  Segments               1
>>  Allocation             inherit
>>  Read ahead sectors     0
>>  Block device           253:8
>> 
seems the lv was not activated, i don't know why, maybe some interaction
with udev?

>> 
>> # mkfs.ext3  /dev/clusterfs/ora1
>> mke2fs 1.38 (30-Jun-2005)
>> mkfs.ext3: Device size reported to be zero.  Invalid partition
>> specified, or
>>        partition table wasn't reread after running fdisk, due to
>>        a modified partition being busy and in use.  You may need to reboot
>>        to re-read your partition table.
>> 
try vgchange -a y again after fixing your lvm.conf as explained above.

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2006-06-17  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16  3:14 [linux-lvm] LVM and Device Mapper C'est Pierre
2006-06-16 13:25 ` Kelly Sauke
2006-06-16 15:14   ` C'est Pierre
2006-06-16 15:20     ` Kelly Sauke
2006-06-17  0:42       ` Luca Berra [this message]
2006-06-20 13:02         ` C'est Pierre
2006-06-16 18:13 ` Zac Slade

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=20060617004234.GB31760@percy.comedia.it \
    --to=bluca@comedia.it \
    --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 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).