[DRBD-user] Trouble with drbd-0.7.19.

Milind Dumbare milind at linsyssoft.com
Wed Jun 14 16:42:20 CEST 2006

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


On Wed, 2006-06-14 at 15:15 +0100, Luciano Miguel Ferreira Rocha wrote:
> On Wed, Jun 14, 2006 at 07:34:56PM +0530, Milind Dumbare wrote:
> > Hi All,
> > 
> > 	I have installed DRBD on my machines ( One is "Dhruva" Fedora Core 5
> > i386 and other is "Tucker" Ubuntu 5.0 x86_64 )
> > I patched Linux-2.6.15 with drbd-0.7.19 patches and installed the
> > kernel. DRBD is built-in in kernel. ( Not Module)
> > 
> > following is my /etc/drbd.conf
> > ===============================
> > resource RES1 {
> >   protocol C;
> >   incon-degr-cmd "wall Beware";
> > 
> >   on dhruva {
> >     device    /dev/drbd0;
> >     disk      /dev/hda8;
> >     address   192.168.1.18:7789;
> >     meta-disk   internal;
> >   }
> >   on tucker {
> >     device    /dev/drbd0;
> >     disk      /dev/sda5;
> >     address   192.168.1.5:7789;
> >     meta-disk   internal;
> >   }
> > }
> > =================================
> > 
> > So as far as I understood "dhruva" is primary and "tucker" is secondary,
> > am I right?
> 
> No. The one that you define as primary, in the command line, gets to be
> primary. There is no default.
> 
So, I will have to do 
	root at dhruva:#drbdadm primary RES1 
And then dhruva will be primary ? 

Do I need to do 
	root at tucker:#drbdadm secondary RES1 
for making tucker partition as secondary?

> > So when I will write any data to /dev/hda8 of dhruva it will be
> > replicated to /dev/sda5, isn't it?
> 
> No. You have to use /dev/drbd0, not the backend devices.
> 
So for replicating data I will have to write data to /dev/drbd0... and
copies will be save susequently to dhruva and tucker?

> > I have /dev/hda8 of Dhruva of 10GB size and /dev/sda5 of Tucker of 21GB
> > size, so it wont cause problem, which is discussed in FAQs, right?
> 
> Yes, you'll be limited to ~ 10GB, though.
> 
Thats fine :-)
Now next problem is. When I do as follows

=====================
[root at dhruva drbd]# drbdadm primary RES1
ioctl(,SET_STATE,) failed: Input/output error
Local replica is inconsistent (--do-what-I-say ?)
Command 'drbdsetup /dev/drbd0 primary' terminated with exit code 21

Broadcast message from root (pts/0) (Wed Jun 14 19:38:32 2006):

Beware
======================
and contents of /proc/drbd  on dhruva are as follows

version: 0.7.19 (api:78/proto:74)
SVN Revision: 2212 build by root at dhruva, 2006-06-14 11:30:40
 0: cs:Connected st:Secondary/Secondary ld:Inconsistent
    ns:0 nr:0 dw:0 dr:0 al:0 bm:608 lo:0 pe:0 ua:0 ap:0
 1: cs:Unconfigured
 2: cs:Unconfigured
 3: cs:Unconfigured
 4: cs:Unconfigured
 5: cs:Unconfigured
 6: cs:Unconfigured
 7: cs:Unconfigured

and that of the tucker are as follow

 0: cs:Connected st:Secondary/Secondary ld:Inconsistent
    ns:0 nr:0 dw:0 dr:0 al:0 bm:3594 lo:0 pe:0 ua:0 ap:0
 1: cs:Unconfigured
 2: cs:Unconfigured
 3: cs:Unconfigured
 4: cs:Unconfigured
 5: cs:Unconfigured
 6: cs:Unconfigured
 7: cs:Unconfigured

so what should I do to get the partition out of Inconsistent state?
Whenever I try to do primary on dhruva..I get the same error.

> > Please help me out with abouve three questions.
> 
> Please read the documentation...
> 
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
-- 
...Milind
KGDB-PRO
http://www.linsyssoft.com/Kgdbpro.html




More information about the drbd-user mailing list