Linux LVM users
 help / color / mirror / Atom feed
From: "Theophanis Kontogiannis" <theophanis_kontogiannis@yahoo.gr>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Issue with clvmd - Is it really bug??
Date: Sat, 5 Jul 2008 22:26:42 +0300	[thread overview]
Message-ID: <01dc01c8ded5$102acd60$30806820$@gr> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1259 bytes --]

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

 

 

 

 

 


[-- Attachment #1.2: Type: text/html, Size: 6860 bytes --]

[-- Attachment #2: ATT00468.txt --]
[-- Type: text/plain, Size: 108 bytes --]

--
Linux-cluster mailing list
Linux-cluster@redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster

                 reply	other threads:[~2008-07-05 19:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='01dc01c8ded5$102acd60$30806820$@gr' \
    --to=theophanis_kontogiannis@yahoo.gr \
    --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