Hi, yes, /dev/VolGroup00/storage is a LV. This is our DRDB device. We configured DRDB as dual primary. So /dev/VolGroup00/storage is equal on both nodes. In serveral Documentations they said that you have to create a pvs/vgs/lvm on DRDB device to use gfs. So this the point where we got stuck. The DRDB Device is in sync. So no problem in this configuration. But when we try to create a pv on the device (actually the lv) this doesnt work. I thought if i create a pv/vg/lv on one node, its automatically created on the second node. Is this right?
Best regards ________________________________ Von: brem belguebli <[email protected]> An: linux clustering <[email protected]> Gesendet: Mittwoch, den 10. März 2010, 20:02:04 Uhr Betreff: Re: [Linux-cluster] Antwort: Re: clvmd does not create vgs It looks there is something I didn't catch from your messages, among them I think I missed the DRBD thing. The /dev/VolGroup00/storage are physical devices (pv's) ? Strange naming as it confuses me to have a VG (VolGroup00) name in it, I tend to read this naming as being a LV (storage being a LV in VG VolGroup00...). Anyway, if possible to have such names for PV's, are you saying that they are different physical devices on each nodes, the one on node1 being the source device of your DRBD setup and the one on node2 being the destination of your DRBD setup ? I don't know much DRBD to help you, but were you expecting DRBD to create the VG storage automatically on the destination PV on node2 ? Brem 2010/3/9 Michael <[email protected]> Hi, > >vgchange -ay didnt help. Here is the output from pvs on both nodes > >[r...@node1 ~]# pvs > > > PV VG Fmt Attr PSize PFree > /dev/VolGroup00/storage storage_cluster lvm2 a- 1,14T 1,14T > > > /dev/sda2 VolGroup00 lvm2 a- 557,62G 0 > /dev/sdb1 VolGroup00 lvm2 a- 1,09T 0 > >[r...@node2 ~]# pvs > > > PV VG Fmt Attr PSize PFree > /dev/VolGroup00/storage lvm2 -- 1,14T 1,14T > /dev/sda2 VolGroup00 lvm2 a- 557,62G 0 > /dev/sdb1 VolGroup00 lvm2 a- 1,09T 0 > >/dev/VolGroup00/storage is my drdb device. I created it on different vg. > > > > > > ________________________________ Von: brem belguebli <[email protected]> > > >An: linux clustering <[email protected]> >Gesendet: Montag, den 8. März 2010, 18:04:28 Uhr >Betreff: Re: [Linux-cluster] Antwort: Re: clvmd does not create vgs > > > >Hi, > >On node1, you created the pv /dev/drbd/by-res/repdata (pvcreate) and added it >to VG storage_cluster (vgcreate ....). > >On node2, as long as the device /dev/drbd/by-res/repdata is accessible, a >simple vgscan would discover the newly created pv and vg. > >If there was a locking issue, it would complain on node2 that it couldn't >activate any LV from storage_cluster. > >Can you post the output of pvs on node2 ? > > >This is how it works for me > >Brem > > >2010/3/8 Bernd Giese <[email protected]> > > >>vgchange -ay on both nodes >> >> >> >> >>brem belguebli <[email protected]> >>Gesendet von: [email protected] >>08.03.2010 13:49 >>Bitte antworten zu >> >> >>linux clustering <[email protected]> >> An linux clustering <[email protected]> >>Kopie >> >>Thema Re: [Linux-cluster] clvmd does not create vgs >> >> >> >> >> >> >> >> >> >>have you tried to pvscan/vgscan on node2 after creation on node1 ? >> >> >>2010/3/8 Michael <[email protected]>: >>>>> no suggestion? >>> >>> Thanks >>> >>> >>> >>> ----- Ursprüngliche Mail ---- >>> Von: Michael <[email protected]> >>>>> An: [email protected] >>> Gesendet: Donnerstag, den 4. März 2010, 11:12:51 Uhr >>> Betreff: [Linux-cluster] clvmd does not create vgs >>>>> >>> Hi, >>> >>> we are curenty using cman, clvmd and drbd. The problem occurs when we want >>> to create volume groups. DRBD shows that both nodes are UpToDate. So first >>> I try create a Physical Volume: >>> >>>>> [r...@node1 log]# pvcreate /dev/drbd/by-res/repdata >>> Physical volume "/dev/drbd/by-res/repdata" successfully created >>> >>> [r...@node2 tmp]# pvs >>> PV VG Fmt Attr PSize PFree >>>>> /dev/VolGroup00/storage lvm2 -- 1,14T 1,14T >>> /dev/sda2 VolGroup00 lvm2 a- 557,62G 0 >>> /dev/sdb1 VolGroup00 lvm2 a- 1,09T 0 >>> >>> Well, /dev/VolGroup00/storage created on both nodes. Fine. Next I want to >>> create a Volume Group: >>>>> >>> [r...@node1 log]# vgcreate storage_cluster /dev/drbd/by-res/repdata >>> vgcreate storage_cluster /dev/drbd0 >>> Clustered volume group "storage_cluster" successfully created >>> >>> [r...@node1 log]# vgs >>>>> VG #PV #LV #SN Attr VSize VFree >>> VolGroup00 2 3 0 wz--n- 1,63T 0 >>> storage_cluster 1 0 0 wz--nc 1,14T 1,14T >>> >>> >>> [r...@node2 tmp]# vgs >>> VG #PV #LV #SN Attr VSize VFree >>>>> VolGroup00 2 3 0 wz--n- 1,63T 0 >>> >>> Hmmm... there is no vg on node2. I restart the whole server but still no vg >>> visible. What could be wrong? >>> >>> We're using Centos 5.4 with all patches installed. >>>>> >>> cman-2.0.115-1.el5_4.9 >>> lvm2-2.02.46-8.el5_4.2 >>> lvm2-cluster-2.02.46-8.el5_4.1 >>> >>> Thanks in advanced and best regards, >>> >>> Michael >>> >>> __________________________________________________ >>>>> Do You Yahoo!? >>> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz >>> gegen Massenmails. >>> http://mail.yahoo.com >>>>> >>> >>> -- >>> Linux-cluster mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/linux-cluster >>>>> >>> >>> __________________________________________________ >>> Do You Yahoo!? >>> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz >>> gegen Massenmails. >>> http://mail.yahoo.com >>>>> >>> >>> -- >>> Linux-cluster mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/linux-cluster >>>>> >> >>-- >>Linux-cluster mailing list >>[email protected] >>https://www.redhat.com/mailman/listinfo/linux-cluster >> >> >>*********************************************************************************** >>Diese E-Mail einschließlich Ihrer Anhänge enthält vertrauliche oder rechtlich >>geschützte >>Informationen. Wenn Sie nicht der beabsichtigte Empfänger sind, informieren >>Sie bitte sofort >>den Absender und löschen Sie diese E-Mail. Das unbefugte Kopieren dieser >>E-Mail oder die >>unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. >> >>The information incl. attachments contained in this message is confidential >>or protected by >>law. If you are not the intended recipient, please contact the sender and >>delete this message. >>Any unauthorised copying of this message or unauthorised distribution of the >>information >>contained herein is prohibited. >>*********************************************************************************** >> >>-- >>Linux-cluster mailing list >>[email protected] >>https://www.redhat.com/mailman/listinfo/linux-cluster >> > > >__________________________________________________ >Do You Yahoo!? >Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen >Massenmails. >http://mail.yahoo.com >-- >Linux-cluster mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/linux-cluster > __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
-- Linux-cluster mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-cluster
