From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m65JUNbv022470 for ; Sat, 5 Jul 2008 15:30:23 -0400 Received: from n6.bullet.mud.yahoo.com (n6.bullet.mud.yahoo.com [216.252.100.57]) by mx3.redhat.com (8.13.8/8.13.8) with SMTP id m65JU3k3023208 for ; Sat, 5 Jul 2008 15:30:03 -0400 From: "Theophanis Kontogiannis" Date: Sat, 5 Jul 2008 22:26:42 +0300 Message-ID: <01dc01c8ded5$102acd60$30806820$@gr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01DD_01C8DEEE.35780560" Content-Language: el Subject: [linux-lvm] Issue with clvmd - Is it really bug?? Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: linux-lvm@redhat.com This is a multipart message in MIME format. ------=_NextPart_000_01DD_01C8DEEE.35780560 Content-Type: multipart/alternative; boundary="----=_NextPart_001_01DE_01C8DEEE.35780560" ------=_NextPart_001_01DE_01C8DEEE.35780560 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Hello all I just found out about this LVM mailing list, so I am posting this also here (already posted in linux-cluster). Hello, I have a 2 node cluster at home with CentOS 5 running on 64bit AMDx2 with DRBD 2.6.18-92.1.6.el5.centos.plus drbd82-8.2.6-1.el5.centos lvm2-2.02.32-4.el5 lvm2-cluster-2.02.32-4.el5 system-config-lvm-1.1.3-2.0.el5 I do not know if my problem is directly related to http://kbase.redhat.com/faq/FAQ_51_10471.shtm and https://bugzilla.redhat.com/show_bug.cgi?id=138396 I do: pvcreate --metadatacopies 2 /dev/drbd0 /dev/drbd1 vgcreate -v vg0 -c y /dev/drbd0 /dev/drbd1 lvcreate -v -L 348G -n data0 vg0 Then I reboot. The LV never becomes available. If I try vgchange -a y I get Error locking on node tweety-1: Volume group for uuid not found: 7Z9ra5zee3ZK7pNpfsblvtMOWXhgkZVEiJrzRQshaaiN5JKtJtkPDkQWfFXYKVVa 0 logical volume(s) in volume group "vg0" now active If I do clvmd -R Then with vgchange -a y vg0. the LV becomes available. Is this really related to the above mentioned bug? How can I make the LV become available during boot up without any intervention? Thank you all for your time, Theophanis Kontogiannis ------=_NextPart_001_01DE_01C8DEEE.35780560 Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable

Hello = all

 

I just = found out about this LVM mailing list, so I am posting this also here (already = posted in linux-cluster).

 

Hello,

 

I have a 2 node cluster at home = with CentOS 5 running on 64bit AMDx2 with DRBD

 

2.6.18-92.1.6.el5.centos.plus

drbd82-8.2.6-1.el5.centos

lvm2-2.02.32-4.el5

lvm2-cluster-2.02.32-4.el5

system-config-lvm-1.1.3-2.0.el5

 

I do not know if my problem is = directly related to http://kbase.redha= t.com/faq/FAQ_51_10471.shtm and https://bug= zilla.redhat.com/show_bug.cgi?id=3D138396

 

I do:

 

pvcreate --metadatacopies 2 /dev/drbd0 /dev/drbd1

vgcreate -v vg0 -c y /dev/drbd0 /dev/drbd1

lvcreate -v -L 348G -n data0 vg0

 

Then I = reboot.

The LV never becomes = available.

 

If I try

 

vgchange -a y

 

I get

 

  Error locking on node tweety-1: Volume group for uuid not found: 7Z9ra5zee3ZK7pNpfsblvtMOWXhgkZVEiJrzRQshaaiN5JKtJtkPDkQWfFXYKVVa

  0 logical volume(s) in volume group "vg0" now = active

 

If I do

 

clvmd –R

 

Then with

 

vgchange –a y vg0.

 

the LV becomes = available.

 

Is this really related to the = above mentioned bug?

 

How can I make the LV become = available during boot up without any intervention?

 

Thank you all for your = time,

 

Theophanis = Kontogiannis

 

 

 

 

 

------=_NextPart_001_01DE_01C8DEEE.35780560-- ------=_NextPart_000_01DD_01C8DEEE.35780560 Content-Type: text/plain; name="ATT00468.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00468.txt" -- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster ------=_NextPart_000_01DD_01C8DEEE.35780560--