Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I suspected the entry was probably not correct. This is the first time I've tried setting this up and was simply following the documentation at http://www.drbd.org/users-guide/s-lvm-lv-as-drbd.html. Thanks for the help. I've made the change and have promoted one node to Primary and will try to run the pvcreate command again when it is done. Thanks Chris ________________________________________ From: drbd-user-bounces at lists.linbit.com [drbd-user-bounces at lists.linbit.com] On Behalf Of haaseg [haaseg at onefreevoice.com] Sent: Thursday, March 20, 2008 8:09 PM To: DRBD Subject: Re: [DRBD-user] DRBD + LVM2 Setup on RHEL5.1 Judging by your pvcreate statement, it appears that you are trying to run lvm2 on top of a drbd device. In that case, I believe /dev/drbd0 needs to be primary before you can run pvcreate. You can put /dev/drbd0 in primary because drbd is not starting correctly. What device is /dev/drbd/r0? Most block devices in RHEL are going to be /dev/sd[a-d] (SCSI or SATA) or /dev/hd[a-d] (IDE). Chris Raver wrote: > > I’m having a difficult time setting up DRBD and LVM2 on Redhat > Enterprise Linux 5.1. I’ve installed DRBD82 and KMOD-DRBD82 via the > CentOS 5.1 repo using yum and I’ve also compiled and installed the > module from source using the correct kernel source, I get the same > result either way. I created my drbd.conf file below but starting the > service fails and so does running pvcreate to create my physical > volume. I’ve been working on this for a couple days with no success. > Can someone here point me in the right direction? > > Starting drbd: > > /etc/init.d/drbd start > > Starting DRBD resources: [ d(r0) Can not open device '/dev/drbd/r0': > No such file or directory > > [r0] cmd /sbin/drbdsetup /dev/drbd0 disk /dev/drbd/r0 /dev/drbd/r0 > internal --set-defaults --create-device --on-io-error=detach failed - > continuing! > > n(r0) ]. > > [root at qa1r2cls drbd-8.2.5]# > > drbd.conf file: > > resource r0 { > > protocol C; > > startup { > > degr-wfc-timeout 90; > > } > > disk { > > on-io-error detach; > > } > > on qa1r2cls { > > device /dev/drbd0; > > disk /dev/drbd/r0; > > meta-disk internal; > > address 192.168.50.202:7789; > > } > > on qa1r3cls { > > device /dev/drbd0; > > disk /dev/drbd/r0; > > meta-disk internal; > > address 192.168.50.203:7789; > > } > > } > > pvcreate error: > > [root at qa1r2cls drbd-8.2.5]# pvcreate -d -v -ff /dev/drbd0 > > Wiping cache of LVM-capable devices > > Wiping internal VG cache > > Device /dev/drbd0 not found (or ignored by filtering). > > lvm.conf filter: > > filter = [ "r|.*|", "a|/dev/drbd[0-9]$|" ] > > * * > > * * > > *Thanks* > > * * > > *cid:image001.jpg at 01C7EA28.A81AF980*** > > *Chris Raver* > > *Senior Quality Assurance Engineer* > > Alpha Bay Corporation > > 150 West Civic Center Drive > > Suite 200 > > Sandy, UT 84070 > > 801-838-7618 > > www.alphabay.com <http://www.alphabay.com> > > *Confidential:* The information in this e-mail message (including any > attachments) is intended only for the use of the recipient(s) named > above and as such is privileged and confidential. If you are not an > intended recipient of this message or an agent responsible for > delivering it to the intended recipient(s), be hereby notified that > you have received this message in error. Any review, dissemination, > distribution, printing or copying of this message is strictly > prohibited. If you believe you have received this message in error, > please notify the sender immediately by return e-mail and delete this > message from your system(s). > > ------------------------------------------------------------------------ > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user