[DRBD-user] drbd r0 fails to start (drbd newbie)

thomas62186218 at aol.com thomas62186218 at aol.com
Mon Jan 14 23:38:25 CET 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hi Lars,

Thank you for the quick response!

The source volume is called /dev/evms/poolvolume1, on 192.168.1.109 
(orionfirst)
The secondary volume is called /dev/evms/poolvolume1b, on 192.168.108 
(orionsecond)

In both case, the device (poolvolume1 and poolvolume1b) are EVMS 
volumes, and those are indeed their actual names.

I changed the hostnames to remove the period characters but still am 
getting the same results.

You say "you cannot claim the whole device". What do you mean by that 
exactly?

Here's the revised drbd.conf, with the same problem, which produces the 
same problem as before.

--------------------------------------
skip {
  As you can see, you can also comment chunks of text
  with a 'skip[optional nonsense]{ skipped text }' section.
  This comes in handy, if you just want to comment out
  some 'resource <some name> {...}' section:
  just precede it with 'skip'.

  The basic format of option assignment is
  <option name><linear whitespace><value>;

  It should be obvious from the examples below,
  but if you really care to know the details:

  <option name> :=
        valid options in the respective scope
  <value>  := <num>|<string>|<choice>|...
              depending on the set of allowed values
              for the respective option.
  <num>    := [0-9]+, sometimes with an optional suffix of K,M,G
  <string> := (<name>|\"([^\"\\\n]*|\\.)*\")+
  <name>   := [/_.A-Za-z0-9-]+
}

global {
    minor-count 254;
    dialog-refresh 1; # 5 seconds
    usage-count no;
    #disable-ip-verification;
}
resource r0 {
    protocol A;
    handlers {
        #pri-on-incon-degr "echo 'Node is primary, degraded and has 
incosistent data' ";
        #pri-lost-after-sb "echo 'node is currently primary, but lost the 
after spllit brain auto recovery procedure' ";
        #outdate-peer "/usr/lib/drbd/outdate-peer.sh on orionfirst 
192.168.1.109 on orionsecond 192.168.1.108";
    }
    startup {
        wfc-timeout 1;
    }
    disk {
    }
    net {
        timeout 60;
        connect-int 10;
        ping-int    10;
        after-sb-1pri   disconnect;
    }
    syncer {
        rate    10M;
        al-extents  257;
    }

    on orionfirst {
        device      /dev/drbd0;
        disk        /dev/evms/pool1vol1;
        address     192.168.1.109:7788;
        meta-disk   internal;
    }

    on orionsecond {
        device      /dev/drbd0;
        disk        /dev/evms/pool1vol1b;
        address     192.168.1.108:7788;
        meta-disk   internal;
    }
 }





-----Original Message-----
From: Lars Ellenberg <lars.ellenberg at linbit.com>
To: drbd-user at lists.linbit.com
Sent: Sun, 13 Jan 2008 10:58 pm
Subject: Re: [DRBD-user] drbd r0 fails to start (drbd newbie)










On Sun, Jan 13, 2008 at 09:41:54PM -0500, thomas62186218 at aol.com wrote:
> Hi all,
>
> I am a new user of drbd 8.0.4 on SLES 10 SP1 with EVMS 2.5.5, and I 
am
> running into what is probably a basic issue but I am missing what the
> cause might be:
>
> ---------------------------
> [root@ ~]# /etc/init.d/drbd start
> Starting DRBD resources:    [ d0 Failure: (114) Lower device is 
already
> claimed. This usually means it is mounted.
>
> cmd /sbin/drbdsetup /dev/drbd0 disk /dev/evms/pool1vol1
> /dev/evms/pool1vol1 internal --set-defaults --create-device  failed -
> continuing!
>
> n0 ].
> ---------------------------
>
> Here is my drbd.conf. Thank you in advance for any guidance!
>
> ---------------------------
> [root@ /etc]# cat drbd.conf
> resource r0 {
>        protocol C;
>        handlers {
>                 #pri-on-incon-degr "echo 'Node is primary, degraded 
and
> has incosistent data' ";
>                 #pri-lost-after-sb "echo 'node is currently primary,
> but lost the after spllit brain auto recovery procedure' ";
>                 #outdate-peer "/usr/lib/drbd/outdate-peer.sh on
> .orionfirst 192.168.1.109 on orionsecond. 192.168.1.108";
>        }
>        startup {
>                wfc-timeout     1;
>        }
>        disk {
>        }
>        net {
>                timeout 60;
>                connect-int     10;
>                ping-int        10;
>                after-sb-1pri   disconnect;
>        }
>        syncer {
>                rate    10M;
>                al-extents      257;
>        }
>
>        on .orionfirst {
>                device      /dev/drbd0;
>                disk        /dev/evms/pool1vol1;

did you mean pool1vol1b?
if that thing is "partitioned",
you cannot claim the whole device.

why do you node names include leading/trailing dots?

>                address     192.168.1.109:7788;
>                meta-disk   internal;
>        }
>
>        on orionsecond. {
>                device      /dev/drbd0;
>                disk        /dev/evms/pool1vol1b;
>                address     192.168.1.108:7788;
>                meta-disk   internal;
>        }
> }

--
: Lars Ellenberg                           http://www.linbit.com :
: DRBD/HA support and consulting             sales at linbit.com :
: LINBIT Information Technologies GmbH      Tel +43-1-8178292-0  :
: Vivenotgasse 48, A-1120 Vienna/Europe     Fax +43-1-8178292-82 :
__
please use the "List-Reply" function of your email client.
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user






________________________________________________________________________
More new features than ever.  Check out the new AOL Mail ! - 
http://webmail.aol.com



More information about the drbd-user mailing list