All of lore.kernel.org
 help / color / mirror / Atom feed
From: Digimer <linux@alteeve.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Milan Broz <mbroz@redhat.com>
Subject: Re: [linux-lvm] Two questions about cluster support (2 problems, actually)
Date: Tue, 16 Mar 2010 22:57:10 -0400	[thread overview]
Message-ID: <4BA04506.3060904@alteeve.com> (raw)
In-Reply-To: <4B9FEF2D.4070608@redhat.com>

On 10-03-16 04:50 PM, Milan Broz wrote:
>> # pvdisplay
>>     connect() failed on local socket: Connection refused
>>     WARNING: Falling back to local file-based locking.
>>     Volume Groups with the clustered attribute will be inaccessible.
>>     "/dev/drbd0" is a new physical volume of "399.99 GB"
>
> apparently clvmd is not running, you cannot see clustered PVs.
>
> Anyway, the DRBD need to setup filters to work properly with lvm2,
> (filter out underlying drbd device)
> (or update to new lvm2 version, RHEL5/CentOS5 build will be available
> in next minor update).
> For more info see https://bugzilla.redhat.com/show_bug.cgi?id=530881
> (not sure it is related, but for archive and other users...)
>
> Milan

Thanks for the reply, Milan!

I had made the change to the 'filter' argument, but I was using 'filter 
= [ "a|drbd.*|", "r|.*|" ]'. I switched to 'filter = [ "a|^/dev/drbd|", 
"a/sd*/", "r/.*/" ]' and started 'clvmd'. This seems to have solved the 
problem, so thank you.

If I may ask another question though;

My DRBD device is '/dev/drbd0' which sits on either node's 
'/dev/san0x/lv02'. When I ran 'pvcreate /dev/drbd0' the PV was created 
successfully and 'pvdisplay' shows the new PV on both nodes. However, I 
see this:

# pvdisplay
   --- Physical volume ---
   PV Name               /dev/sda2
   VG Name               san02
   PV Size               465.51 GB / not usable 14.52 MB
   Allocatable           yes
   PE Size (KByte)       32768
   Total PE              14896
   Free PE               1407
   Allocated PE          13489
   PV UUID               ru7tmz-Qd4d-aatg-4ReY-TPPq-gMll-Z5ZOkL

   "/dev/san02/lv02" is a new physical volume of "399.99 GB"
   --- NEW Physical volume ---
   PV Name               /dev/san02/lv02
   VG Name
   PV Size               399.99 GB
   Allocatable           NO
   PE Size (KByte)       0
   Total PE              0
   Free PE               0
   Allocated PE          0
   PV UUID               MjwXhY-T3dw-IUkI-ZdSI-FKEB-KJdq-nl9GUo

Note that the 'PV Name' is '/dev/san02/lv02' but the device passed was 
'pvcreate /dev/drbd0'. Is this correct? I'd expect it to show the DRBD 
device, not the DRBD's underlying logical volume.

-- 
Digimer
E-Mail:         linux@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

  reply	other threads:[~2010-03-17  2:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 19:23 [linux-lvm] Two questions about cluster support (2 problems, actually) Digimer
2010-03-16 20:50 ` Milan Broz
2010-03-17  2:57   ` Digimer [this message]
2010-03-17  3:50     ` [linux-lvm] Fixed! (was: Re: Two questions about cluster support (2 problems, actually)) Digimer

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=4BA04506.3060904@alteeve.com \
    --to=linux@alteeve.com \
    --cc=linux-lvm@redhat.com \
    --cc=mbroz@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.