Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
>From your configuration you have :
[...]
device /dev/drbd0;
disk /dev/drbd/r0;
[...]
I would really be surprised that your disk device is /dev/drbd/r0 . It
should be something like /dev/hdaX or /dev/sdaX or
/dev/cciss/c0d0s0[...] (where X is a number) or whatever empty block
device you want to use as storage (could be AoE device through
/dev/etherd/e0.0). It can also be a logicial block device such as a
md-device (ie: /dev/md0).
The disk option is to define the underlying block device where you
data will be stored. This is kinda a basic configuration option, you
should really read the online manual.
DO NOT TRY RANDOM VALUES, you can wipe your operating system data if
you force a wrong value (drbd will fight kinda hard against such
stupid error, but still, you should be 100% sure of your value)
Once this configuration error is corrected, you will be able to create
the /dev/drbd0 device and set as a physical volume for lvm (with
pvcreate). The rest should go smoothly.
Pascal Charest
--
Pascal Charest, Free software consultant (GNU/linux)
http://blog.pacharest.com & http://www.mass-storage.org
On Thu, Mar 20, 2008 at 7:02 PM, Chris Raver <chris at alphabay.com> 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
>
>
>
>
>
> 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
>
>
>
> 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
>
>