Forwarding messages that missed the list:
----- Original Message -----
> From: "Nick Khamis" <[email protected]>
> To: "Jake Smith" <[email protected]>
> Sent: Tuesday, September 20, 2011 3:16:17 PM
> Subject: Re: [DRBD-user] DRBD RA Error
>
> Hello Jake,
>
> Thank you so much for your response.
Np. I've had help here - glad to pass it along.
> Yes, the "linbitt" is just a
> typo
> in the email. I am using the deprecated Heartebeat drbd RA to fix
> other issues... In terms of the DRBD status versus actual resource
> name, the resource is actually:
>
> resource r0.res {
> device /dev/drbd0;
> disk /dev/sda8;
> meta-disk /dev/sda7 [0];
> on mydrbd1 {
> address 192.168.2.105:7789;
> }
> on mydrbd2 {
> address 192.168.2.106:7789;
> }
> }
>
I know not about the Heartbeat drbd RA so I'm afraid I can't be of much more
help.
> root@mydrbd1:/# /etc/init.d/drbd status
> drbd driver loaded OK; device status:
> version: 8.3.7 (api:88/proto:86-91)
> srcversion: EE47D8BF18AC166BE219757
> m:res cs ro ds p mounted
> fstype
> 0:r0_res Connected Primary/Secondary UpToDate/UpToDate C
> /service ext3
>
> root@mydrbd1:/# drbdadm attach r0_res
> 'r0_res' not defined in your config.
>
> And /dev/drbd/by-res/ contains r0.res, which is an empty when opening
> it with nano?
Try $ls -la /dev/drbd/by-res/
You'll find that those empty files are actually symbolic links to the drbd disk
/dev/drbdX (drbd0 probably in this case)
*snip*
Jake
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
