Xen users - Feb 2013 - Remus disk replication failed

Dear all,

I am configure my machine to run the remus disk replication. I am using xen
4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and
DomU.
I have install the blktap and its work properly with configuration string
phy or tap2 like this :
disk = [''phy:/dev/vggroup/DomU,xvda,w'']
or
disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']

and remus command

remus --no-net myvm mybackuphost


However when I change the string as suggested on remus pages to enable the
disk replication its still failed :

name = "DomU"
memory = 1024
disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
vif = [''ip=192.168.1.55,bridge=xenbr0'']
bootloader = "pygrub"

with error messages :

name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
Using config file "/etc/xen/DomU.cfg".
Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
(512  )

and on the log file :


name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
    mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line 3987, in create_vbd
    devid = dev_control.createDevice(config)
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 174, in createDevice
    device = TapdiskController.create(params, file)
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 286, in create
    return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 233, in exc
    (args, rc, out, err))
TapdiskException: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )

Any hints and help would very appreciated.

Regards,

Agya


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Dear all,

I am configure my machine to run the remus disk replication. I am using xen
4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and
DomU.
I have install the blktap and its work properly with configuration string
phy or tap2 like this :
disk = [''phy:/dev/vggroup/DomU,xvda,w'']
or
disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']

and remus command

remus --no-net myvm mybackuphost


However when I change the string as suggested on remus pages to enable the
disk replication its still failed :

name = "DomU"
memory = 1024
disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
vif = [''ip=192.168.1.55,bridge=xenbr0'']
bootloader = "pygrub"

with error messages :

name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
Using config file "/etc/xen/DomU.cfg".
Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
(512  )

and on the log file :


name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
    mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line 3987, in create_vbd
    devid = dev_control.createDevice(config)
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 174, in createDevice
    device = TapdiskController.create(params, file)
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 286, in create
    return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
  File
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
line 233, in exc
    (args, rc, out, err))
TapdiskException: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )

Any hints and help would very appreciated.

Regards,

Agya


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Hello, Anyone have a clue? I have tried but still failed :(

On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> wrote:
> Dear all,
>
> I am configure my machine to run the remus disk replication. I am using
> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and
> DomU.
> I have install the blktap and its work properly with configuration string
> phy or tap2 like this :
> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> or
> disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>
> and remus command
>
> remus --no-net myvm mybackuphost
>
>
> However when I change the string as suggested on remus pages to enable the
> disk replication its still failed :
>
> name = "DomU"
> memory = 1024
> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> bootloader = "pygrub"
>
> with error messages :
>
> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> Using config file "/etc/xen/DomU.cfg".
> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
> (512  )
>
> and on the log file :
>
>
> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line
> 3987, in create_vbd
>     devid = dev_control.createDevice(config)
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 174, in createDevice
>     device = TapdiskController.create(params, file)
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 286, in create
>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 233, in exc
>     (args, rc, out, err))
> TapdiskException: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> failed (512  )
>
> Any hints and help would very appreciated.
>
> Regards,
>
> Agya
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Hello, Anyone have a clue? I have tried but still failed :(

On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com> wrote:
> Dear all,
>
> I am configure my machine to run the remus disk replication. I am using
> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0 and
> DomU.
> I have install the blktap and its work properly with configuration string
> phy or tap2 like this :
> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> or
> disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>
> and remus command
>
> remus --no-net myvm mybackuphost
>
>
> However when I change the string as suggested on remus pages to enable the
> disk replication its still failed :
>
> name = "DomU"
> memory = 1024
> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> bootloader = "pygrub"
>
> with error messages :
>
> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> Using config file "/etc/xen/DomU.cfg".
> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
> (512  )
>
> and on the log file :
>
>
> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line
> 3987, in create_vbd
>     devid = dev_control.createDevice(config)
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 174, in createDevice
>     device = TapdiskController.create(params, file)
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 286, in create
>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>   File
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> line 233, in exc
>     (args, rc, out, err))
> TapdiskException: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> failed (512  )
>
> Any hints and help would very appreciated.
>
> Regards,
>
> Agya
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

hi
 sorry for the delayed response. IIRC the blktap2 driver required for
tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
 I havent used it in a long time myself. I suggest trying disk
replication with DRBD.

thanks
shriram

On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com>
wrote:
> Hello, Anyone have a clue? I have tried but still failed :(
>
> On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com>
wrote:
>>
>> Dear all,
>>
>> I am configure my machine to run the remus disk replication. I am using
>> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0
and
>> DomU.
>> I have install the blktap and its work properly with configuration
string
>> phy or tap2 like this :
>> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
>> or
>> disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>>
>> and remus command
>>
>> remus --no-net myvm mybackuphost
>>
>>
>> However when I change the string as suggested on remus pages to enable
the
>> disk replication its still failed :
>>
>> name = "DomU"
>> memory = 1024
>> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> vif = [''ip=192.168.1.55,bridge=xenbr0'']
>> bootloader = "pygrub"
>>
>> with error messages :
>>
>> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> Using config file "/etc/xen/DomU.cfg".
>> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
>> (512  )
>>
>> and on the log file :
>>
>>
>> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line
>> 3987, in create_vbd
>>     devid = dev_control.createDevice(config)
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 174, in createDevice
>>     device = TapdiskController.create(params, file)
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 286, in create
>>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 233, in exc
>>     (args, rc, out, err))
>> TapdiskException: (''create'',
>> ''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )
>>
>> Any hints and help would very appreciated.
>>
>> Regards,
>>
>> Agya
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

hi
 sorry for the delayed response. IIRC the blktap2 driver required for
tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
 I havent used it in a long time myself. I suggest trying disk
replication with DRBD.

thanks
shriram

On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <herydians@gmail.com>
wrote:
> Hello, Anyone have a clue? I have tried but still failed :(
>
> On Sat, Feb 16, 2013 at 6:56 PM, agya naila <agya.naila@gmail.com>
wrote:
>>
>> Dear all,
>>
>> I am configure my machine to run the remus disk replication. I am using
>> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for Dom0
and
>> DomU.
>> I have install the blktap and its work properly with configuration
string
>> phy or tap2 like this :
>> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
>> or
>> disk = [''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>>
>> and remus command
>>
>> remus --no-net myvm mybackuphost
>>
>>
>> However when I change the string as suggested on remus pages to enable
the
>> disk replication its still failed :
>>
>> name = "DomU"
>> memory = 1024
>> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> vif = [''ip=192.168.1.55,bridge=xenbr0'']
>> bootloader = "pygrub"
>>
>> with error messages :
>>
>> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> Using config file "/etc/xen/DomU.cfg".
>> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed
>> (512  )
>>
>> and on the log file :
>>
>>
>> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
line
>> 3987, in create_vbd
>>     devid = dev_control.createDevice(config)
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 174, in createDevice
>>     device = TapdiskController.create(params, file)
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 286, in create
>>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>>   File
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> line 233, in exc
>>     (args, rc, out, err))
>> TapdiskException: (''create'',
>> ''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )
>>
>> Any hints and help would very appreciated.
>>
>> Regards,
>>
>> Agya
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> hi
>
Thank you shriram.

>  sorry for the delayed response. IIRC the blktap2 driver required for
> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
>  I havent used it in a long time myself. I suggest trying disk
> replication with DRBD.
>
>
I am also found some information here
http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem
on amd64 architecture. I have tried to install and configure the DRBD but
its didn''t connect each other.
I used drbd-8.3.11-remus and installed as follow

cd /usr/src/
wget
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
tar xzf drbd-8.3.9-remus.tar.gz
chown -R root:root drbd-8.3-remus
cd /usr/src/drbd-8.3-remus
chmod 777 autogen.sh
./autogen.sh
dpkg-buildpackage -b -uc
cd /usr/src/drbd-8.3-remus/drbd
make clean
make
make install
cd /usr/src/
cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
/etc/drbd.d/global_common.conf
cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
/etc/drbd.d/SystemHA_protoD.res

sudo apt-get install drbd8-utils

 from tutorial http://remusha.wikidot.com/configuring-and-installing-remus

My *.res configuration as follow :

resource drbd-vm{
  device    /dev/drbd1;
  disk      /dev/vgvoip/DomU;
  meta-disk internal;
  on machine1 {
    address   10.10.10.1:7789;
  }
  on machine2 {
    address   10.10.10.3:7789;
  }
}

and then I invoke command to create that meta

drbdadm create-md drbd-vm

However, when I try to make this configuration up by :

drbdadm up drbd-vm

Its come with error :

$ sudo drbdadm up drbd-vm
1: Failure: (124) Device is attached to a disk (use detach first)
Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal
--set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on'' terminated with exit code 10

If I run the

$ sudo drbdadm detach drbd-vm

Its come error

$ sudo drbdadm detach drbd-vm
1: State change failed: (-2) Need access to UpToDate data
Command ''drbdsetup 1 detach'' terminated with exit code 17

Here the /proc/drbd on both machine

Machine 1

$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine1, 2013-02-18 18:49:57

 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0 chkpt:0 oos:10485404


Machine 2

$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine2, 2013-02-18 19:26:57

 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
chkpt:0 oos:10485404


Do you have some hints?

Thank you,


Agya


thanks
> shriram
>
> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com>
> wrote:
> > Hello, Anyone have a clue? I have tried but still failed :(
> >
> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
> wrote:
> >>
> >> Dear all,
> >>
> >> I am configure my machine to run the remus disk replication. I am
using
> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for
Dom0
> and
> >> DomU.
> >> I have install the blktap and its work properly with configuration
> string
> >> phy or tap2 like this :
> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> >> or
> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
> >>
> >> and remus command
> >>
> >> remus --no-net myvm mybackuphost
> >>
> >>
> >> However when I change the string as suggested on remus pages to
enable
> the
> >> disk replication its still failed :
> >>
> >> name = "DomU"
> >> memory = 1024
> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> >> bootloader = "pygrub"
> >>
> >> with error messages :
> >>
> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> >> Using config file "/etc/xen/DomU.cfg".
> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> failed
> >> (512  )
> >>
> >> and on the log file :
> >>
> >>
> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
> >>   File
> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
> line
> >> 3987, in create_vbd
> >>     devid = dev_control.createDevice(config)
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 174, in createDevice
> >>     device = TapdiskController.create(params, file)
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 286, in create
> >>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 233, in exc
> >>     (args, rc, out, err))
> >> TapdiskException: (''create'',
> >> ''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )
> >>
> >> Any hints and help would very appreciated.
> >>
> >> Regards,
> >>
> >> Agya
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> >>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> hi
>
Thank you shriram.

>  sorry for the delayed response. IIRC the blktap2 driver required for
> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
>  I havent used it in a long time myself. I suggest trying disk
> replication with DRBD.
>
>
I am also found some information here
http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem
on amd64 architecture. I have tried to install and configure the DRBD but
its didn''t connect each other.
I used drbd-8.3.11-remus and installed as follow

cd /usr/src/
wget
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
tar xzf drbd-8.3.9-remus.tar.gz
chown -R root:root drbd-8.3-remus
cd /usr/src/drbd-8.3-remus
chmod 777 autogen.sh
./autogen.sh
dpkg-buildpackage -b -uc
cd /usr/src/drbd-8.3-remus/drbd
make clean
make
make install
cd /usr/src/
cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
/etc/drbd.d/global_common.conf
cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
/etc/drbd.d/SystemHA_protoD.res

sudo apt-get install drbd8-utils

 from tutorial http://remusha.wikidot.com/configuring-and-installing-remus

My *.res configuration as follow :

resource drbd-vm{
  device    /dev/drbd1;
  disk      /dev/vgvoip/DomU;
  meta-disk internal;
  on machine1 {
    address   10.10.10.1:7789;
  }
  on machine2 {
    address   10.10.10.3:7789;
  }
}

and then I invoke command to create that meta

drbdadm create-md drbd-vm

However, when I try to make this configuration up by :

drbdadm up drbd-vm

Its come with error :

$ sudo drbdadm up drbd-vm
1: Failure: (124) Device is attached to a disk (use detach first)
Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU internal
--set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on'' terminated with exit code 10

If I run the

$ sudo drbdadm detach drbd-vm

Its come error

$ sudo drbdadm detach drbd-vm
1: State change failed: (-2) Need access to UpToDate data
Command ''drbdsetup 1 detach'' terminated with exit code 17

Here the /proc/drbd on both machine

Machine 1

$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine1, 2013-02-18 18:49:57

 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0 chkpt:0 oos:10485404


Machine 2

$ sudo cat /proc/drbd
version: 8.3.11 (api:88/proto:86-96)
GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine2, 2013-02-18 19:26:57

 1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
chkpt:0 oos:10485404


Do you have some hints?

Thank you,


Agya


thanks
> shriram
>
> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com>
> wrote:
> > Hello, Anyone have a clue? I have tried but still failed :(
> >
> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
> wrote:
> >>
> >> Dear all,
> >>
> >> I am configure my machine to run the remus disk replication. I am
using
> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both for
Dom0
> and
> >> DomU.
> >> I have install the blktap and its work properly with configuration
> string
> >> phy or tap2 like this :
> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> >> or
> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
> >>
> >> and remus command
> >>
> >> remus --no-net myvm mybackuphost
> >>
> >>
> >> However when I change the string as suggested on remus pages to
enable
> the
> >> disk replication its still failed :
> >>
> >> name = "DomU"
> >> memory = 1024
> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> >> bootloader = "pygrub"
> >>
> >> with error messages :
> >>
> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> >> Using config file "/etc/xen/DomU.cfg".
> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> failed
> >> (512  )
> >>
> >> and on the log file :
> >>
> >>
> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
> >>   File
> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
> line
> >> 3987, in create_vbd
> >>     devid = dev_control.createDevice(config)
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 174, in createDevice
> >>     device = TapdiskController.create(params, file)
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 286, in create
> >>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
> >>   File
> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> line 233, in exc
> >>     (args, rc, out, err))
> >> TapdiskException: (''create'',
> >> ''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
failed (512  )
> >>
> >> Any hints and help would very appreciated.
> >>
> >> Regards,
> >>
> >> Agya
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> >>
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hi,
 I suggest you read up on the DRBD setup documentation from the
drbd.org website.
 The setup procedure is same. You can later flip to the remus
replication protocol by simply
 changing the protocol type (C to D).

thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com>
wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>>  sorry for the delayed response. IIRC the blktap2 driver required for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
>>  I havent used it in a long time myself. I suggest trying disk
>> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem
on
> amd64 architecture. I have tried to install and configure the DRBD but its
> didn''t connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
>  from tutorial http://remusha.wikidot.com/configuring-and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
>   device    /dev/drbd1;
>   disk      /dev/vgvoip/DomU;
>   meta-disk internal;
>   on machine1 {
>     address   10.10.10.1:7789;
>   }
>   on machine2 {
>     address   10.10.10.3:7789;
>   }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU
internal
> --set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on''
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command ''drbdsetup 1 detach'' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1,
> 2013-02-18 18:49:57
>
>  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
>     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2,
> 2013-02-18 19:26:57
>
>  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
>     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com>
>> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :(
>> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replication. I
am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both
for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with
configuration
>> >> string
>> >> phy or tap2 like this :
>> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
>> >> or
>> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pages
to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name = "DomU"
>> >> memory = 1024
>> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
>> >> bootloader = "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>> >> failed
>> >> (512  )
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>> >>   File
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >>     devid = dev_control.createDevice(config)
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 174, in createDevice
>> >>     device = TapdiskController.create(params, file)
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 286, in create
>> >>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 233, in exc
>> >>     (args, rc, out, err))
>> >> TapdiskException: (''create'',
>> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xen.org
>> > http://lists.xen.org/xen-devel
>> >
>
>

Hi,
 I suggest you read up on the DRBD setup documentation from the
drbd.org website.
 The setup procedure is same. You can later flip to the remus
replication protocol by simply
 changing the protocol type (C to D).

thanks
shriram

On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com>
wrote:
>
> On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>
> wrote:
>>
>> hi
>
>
> Thank you shriram.
>
>>
>>  sorry for the delayed response. IIRC the blktap2 driver required for
>> tapdisk replication doesnt exist in the mainstream dom0 kernels, IIRC.
>>  I havent used it in a long time myself. I suggest trying disk
>> replication with DRBD.
>>
>
> I am also found some information here
> http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2 problem
on
> amd64 architecture. I have tried to install and configure the DRBD but its
> didn''t connect each other.
> I used drbd-8.3.11-remus and installed as follow
>
> cd /usr/src/
> wget
>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
> tar xzf drbd-8.3.9-remus.tar.gz
> chown -R root:root drbd-8.3-remus
> cd /usr/src/drbd-8.3-remus
> chmod 777 autogen.sh
> ./autogen.sh
> dpkg-buildpackage -b -uc
> cd /usr/src/drbd-8.3-remus/drbd
> make clean
> make
> make install
> cd /usr/src/
> cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> /etc/drbd.d/global_common.conf
> cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> /etc/drbd.d/SystemHA_protoD.res
>
> sudo apt-get install drbd8-utils
>
>  from tutorial http://remusha.wikidot.com/configuring-and-installing-remus
>
> My *.res configuration as follow :
>
> resource drbd-vm{
>   device    /dev/drbd1;
>   disk      /dev/vgvoip/DomU;
>   meta-disk internal;
>   on machine1 {
>     address   10.10.10.1:7789;
>   }
>   on machine2 {
>     address   10.10.10.3:7789;
>   }
> }
>
> and then I invoke command to create that meta
>
> drbdadm create-md drbd-vm
>
> However, when I try to make this configuration up by :
>
> drbdadm up drbd-vm
>
> Its come with error :
>
> $ sudo drbdadm up drbd-vm
> 1: Failure: (124) Device is attached to a disk (use detach first)
> Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU
internal
> --set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on''
> terminated with exit code 10
>
> If I run the
>
> $ sudo drbdadm detach drbd-vm
>
> Its come error
>
> $ sudo drbdadm detach drbd-vm
> 1: State change failed: (-2) Need access to UpToDate data
> Command ''drbdsetup 1 detach'' terminated with exit code 17
>
> Here the /proc/drbd on both machine
>
> Machine 1
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine1,
> 2013-02-18 18:49:57
>
>  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
>     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> chkpt:0 oos:10485404
>
>
> Machine 2
>
> $ sudo cat /proc/drbd
> version: 8.3.11 (api:88/proto:86-96)
> GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by root@machine2,
> 2013-02-18 19:26:57
>
>  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown   r----s
>     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> chkpt:0 oos:10485404
>
>
> Do you have some hints?
>
> Thank you,
>
>
> Agya
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com>
>> wrote:
>> > Hello, Anyone have a clue? I have tried but still failed :(
>> >
>> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I am configure my machine to run the remus disk replication. I
am using
>> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit both
for Dom0
>> >> and
>> >> DomU.
>> >> I have install the blktap and its work properly with
configuration
>> >> string
>> >> phy or tap2 like this :
>> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
>> >> or
>> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>> >>
>> >> and remus command
>> >>
>> >> remus --no-net myvm mybackuphost
>> >>
>> >>
>> >> However when I change the string as suggested on remus pages
to enable
>> >> the
>> >> disk replication its still failed :
>> >>
>> >> name = "DomU"
>> >> memory = 1024
>> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
>> >> bootloader = "pygrub"
>> >>
>> >> with error messages :
>> >>
>> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> Using config file "/etc/xen/DomU.cfg".
>> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>> >> failed
>> >> (512  )
>> >>
>> >> and on the log file :
>> >>
>> >>
>> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
>> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>> >>   File
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>> >> line
>> >> 3987, in create_vbd
>> >>     devid = dev_control.createDevice(config)
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 174, in createDevice
>> >>     device = TapdiskController.create(params, file)
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 286, in create
>> >>     return TapdiskController.exc(''create'',
''-a%s:%s'' % (dtype, image))
>> >>   File
>> >>
>> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> line 233, in exc
>> >>     (args, rc, out, err))
>> >> TapdiskException: (''create'',
>> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>> >>
>> >> Any hints and help would very appreciated.
>> >>
>> >> Regards,
>> >>
>> >> Agya
>> >>
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> >>
>> >
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xen.org
>> > http://lists.xen.org/xen-devel
>> >
>
>

On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> Hi,
>  I suggest you read up on the DRBD setup documentation from the
> drbd.org website.
>  The setup procedure is same. You can later flip to the remus
> replication protocol by simply
>  changing the protocol type (C to D).
>
> I am comparing my configuration with drbd website, however I got this
error :

$ sudo drbdadm up drbd-vm
*''D'' is no valid protocol.*
*Command ''drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D
--set-defaults --create-device --rr-conflict=disconnect
--after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
--after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4
--max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
--ping-timeout=20 --ping-int=3 --timeout=30'' terminated with exit code
20*
*drbdadm connect drbd-vm: exited with code 20*
*
*
$ sudo drbd-overview
  1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya


> thanks
> shriram
>
> On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com>
wrote:
> >
> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca
> >
> > wrote:
> >>
> >> hi
> >
> >
> > Thank you shriram.
> >
> >>
> >>  sorry for the delayed response. IIRC the blktap2 driver required
for
> >> tapdisk replication doesnt exist in the mainstream dom0 kernels,
IIRC.
> >>  I havent used it in a long time myself. I suggest trying disk
> >> replication with DRBD.
> >>
> >
> > I am also found some information here
> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2
> problem on
> > amd64 architecture. I have tried to install and configure the DRBD but
> its
> > didn''t connect each other.
> > I used drbd-8.3.11-remus and installed as follow
> >
> > cd /usr/src/
> > wget
> >
>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
> > tar xzf drbd-8.3.9-remus.tar.gz
> > chown -R root:root drbd-8.3-remus
> > cd /usr/src/drbd-8.3-remus
> > chmod 777 autogen.sh
> > ./autogen.sh
> > dpkg-buildpackage -b -uc
> > cd /usr/src/drbd-8.3-remus/drbd
> > make clean
> > make
> > make install
> > cd /usr/src/
> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> > /etc/drbd.d/global_common.conf
> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> > /etc/drbd.d/SystemHA_protoD.res
> >
> > sudo apt-get install drbd8-utils
> >
> >  from tutorial
> http://remusha.wikidot.com/configuring-and-installing-remus
> >
> > My *.res configuration as follow :
> >
> > resource drbd-vm{
> >   device    /dev/drbd1;
> >   disk      /dev/vgvoip/DomU;
> >   meta-disk internal;
> >   on machine1 {
> >     address   10.10.10.1:7789;
> >   }
> >   on machine2 {
> >     address   10.10.10.3:7789;
> >   }
> > }
> >
> > and then I invoke command to create that meta
> >
> > drbdadm create-md drbd-vm
> >
> > However, when I try to make this configuration up by :
> >
> > drbdadm up drbd-vm
> >
> > Its come with error :
> >
> > $ sudo drbdadm up drbd-vm
> > 1: Failure: (124) Device is attached to a disk (use detach first)
> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU
internal
> > --set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on''
> > terminated with exit code 10
> >
> > If I run the
> >
> > $ sudo drbdadm detach drbd-vm
> >
> > Its come error
> >
> > $ sudo drbdadm detach drbd-vm
> > 1: State change failed: (-2) Need access to UpToDate data
> > Command ''drbdsetup 1 detach'' terminated with exit
code 17
> >
> > Here the /proc/drbd on both machine
> >
> > Machine 1
> >
> > $ sudo cat /proc/drbd
> > version: 8.3.11 (api:88/proto:86-96)
> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine1
> ,
> > 2013-02-18 18:49:57
> >
> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
> > chkpt:0 oos:10485404
> >
> >
> > Machine 2
> >
> > $ sudo cat /proc/drbd
> > version: 8.3.11 (api:88/proto:86-96)
> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine2
> ,
> > 2013-02-18 19:26:57
> >
> >  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown  
r----s
> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> > chkpt:0 oos:10485404
> >
> >
> > Do you have some hints?
> >
> > Thank you,
> >
> >
> > Agya
> >
> >
> >> thanks
> >> shriram
> >>
> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com
> >
> >> wrote:
> >> > Hello, Anyone have a clue? I have tried but still failed :(
> >> >
> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
> >> > wrote:
> >> >>
> >> >> Dear all,
> >> >>
> >> >> I am configure my machine to run the remus disk
replication. I am
> using
> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit
both for
> Dom0
> >> >> and
> >> >> DomU.
> >> >> I have install the blktap and its work properly with
configuration
> >> >> string
> >> >> phy or tap2 like this :
> >> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> >> >> or
> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
> >> >>
> >> >> and remus command
> >> >>
> >> >> remus --no-net myvm mybackuphost
> >> >>
> >> >>
> >> >> However when I change the string as suggested on remus
pages to
> enable
> >> >> the
> >> >> disk replication its still failed :
> >> >>
> >> >> name = "DomU"
> >> >> memory = 1024
> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> >> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> >> >> bootloader = "pygrub"
> >> >>
> >> >> with error messages :
> >> >>
> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> >> >> Using config file "/etc/xen/DomU.cfg".
> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> >> >> failed
> >> >> (512  )
> >> >>
> >> >> and on the log file :
> >> >>
> >> >>
> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
> >> >>   File
> >> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
> >> >> line
> >> >> 3987, in create_vbd
> >> >>     devid = dev_control.createDevice(config)
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 174, in createDevice
> >> >>     device = TapdiskController.create(params, file)
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 286, in create
> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
> image))
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 233, in exc
> >> >>     (args, rc, out, err))
> >> >> TapdiskException: (''create'',
> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
> >> >>
> >> >> Any hints and help would very appreciated.
> >> >>
> >> >> Regards,
> >> >>
> >> >> Agya
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@lists.xen.org
> >> >> http://lists.xen.org/xen-devel
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Xen-devel mailing list
> >> > Xen-devel@lists.xen.org
> >> > http://lists.xen.org/xen-devel
> >> >
> >
> >
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
> Hi,
>  I suggest you read up on the DRBD setup documentation from the
> drbd.org website.
>  The setup procedure is same. You can later flip to the remus
> replication protocol by simply
>  changing the protocol type (C to D).
>
> I am comparing my configuration with drbd website, however I got this
error :

$ sudo drbdadm up drbd-vm
*''D'' is no valid protocol.*
*Command ''drbdsetup 1 net ipv4:10.10.10.1:7789 ipv4:10.10.10.3:7789 D
--set-defaults --create-device --rr-conflict=disconnect
--after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
--after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4
--max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
--ping-timeout=20 --ping-int=3 --timeout=30'' terminated with exit code
20*
*drbdadm connect drbd-vm: exited with code 20*
*
*
$ sudo drbd-overview
  1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s

Thank you,

Agya


> thanks
> shriram
>
> On Mon, Feb 18, 2013 at 4:11 PM, agya naila <agya.naila@gmail.com>
wrote:
> >
> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca
> >
> > wrote:
> >>
> >> hi
> >
> >
> > Thank you shriram.
> >
> >>
> >>  sorry for the delayed response. IIRC the blktap2 driver required
for
> >> tapdisk replication doesnt exist in the mainstream dom0 kernels,
IIRC.
> >>  I havent used it in a long time myself. I suggest trying disk
> >> replication with DRBD.
> >>
> >
> > I am also found some information here
> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2
> problem on
> > amd64 architecture. I have tried to install and configure the DRBD but
> its
> > didn''t connect each other.
> > I used drbd-8.3.11-remus and installed as follow
> >
> > cd /usr/src/
> > wget
> >
>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
> > tar xzf drbd-8.3.9-remus.tar.gz
> > chown -R root:root drbd-8.3-remus
> > cd /usr/src/drbd-8.3-remus
> > chmod 777 autogen.sh
> > ./autogen.sh
> > dpkg-buildpackage -b -uc
> > cd /usr/src/drbd-8.3-remus/drbd
> > make clean
> > make
> > make install
> > cd /usr/src/
> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
> > /etc/drbd.d/global_common.conf
> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
> > /etc/drbd.d/SystemHA_protoD.res
> >
> > sudo apt-get install drbd8-utils
> >
> >  from tutorial
> http://remusha.wikidot.com/configuring-and-installing-remus
> >
> > My *.res configuration as follow :
> >
> > resource drbd-vm{
> >   device    /dev/drbd1;
> >   disk      /dev/vgvoip/DomU;
> >   meta-disk internal;
> >   on machine1 {
> >     address   10.10.10.1:7789;
> >   }
> >   on machine2 {
> >     address   10.10.10.3:7789;
> >   }
> > }
> >
> > and then I invoke command to create that meta
> >
> > drbdadm create-md drbd-vm
> >
> > However, when I try to make this configuration up by :
> >
> > drbdadm up drbd-vm
> >
> > Its come with error :
> >
> > $ sudo drbdadm up drbd-vm
> > 1: Failure: (124) Device is attached to a disk (use detach first)
> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU /dev/vgvoip/DomU
internal
> > --set-defaults --create-device --fencing=dont-care
--on-io-error=pass_on''
> > terminated with exit code 10
> >
> > If I run the
> >
> > $ sudo drbdadm detach drbd-vm
> >
> > Its come error
> >
> > $ sudo drbdadm detach drbd-vm
> > 1: State change failed: (-2) Need access to UpToDate data
> > Command ''drbdsetup 1 detach'' terminated with exit
code 17
> >
> > Here the /proc/drbd on both machine
> >
> > Machine 1
> >
> > $ sudo cat /proc/drbd
> > version: 8.3.11 (api:88/proto:86-96)
> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine1
> ,
> > 2013-02-18 18:49:57
> >
> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
> > chkpt:0 oos:10485404
> >
> >
> > Machine 2
> >
> > $ sudo cat /proc/drbd
> > version: 8.3.11 (api:88/proto:86-96)
> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
root@machine2
> ,
> > 2013-02-18 19:26:57
> >
> >  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown  
r----s
> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b def:0
> > chkpt:0 oos:10485404
> >
> >
> > Do you have some hints?
> >
> > Thank you,
> >
> >
> > Agya
> >
> >
> >> thanks
> >> shriram
> >>
> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama
<herydians@gmail.com
> >
> >> wrote:
> >> > Hello, Anyone have a clue? I have tried but still failed :(
> >> >
> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
> >> > wrote:
> >> >>
> >> >> Dear all,
> >> >>
> >> >> I am configure my machine to run the remus disk
replication. I am
> using
> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64 bit
both for
> Dom0
> >> >> and
> >> >> DomU.
> >> >> I have install the blktap and its work properly with
configuration
> >> >> string
> >> >> phy or tap2 like this :
> >> >> disk = [''phy:/dev/vggroup/DomU,xvda,w'']
> >> >> or
> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
> >> >>
> >> >> and remus command
> >> >>
> >> >> remus --no-net myvm mybackuphost
> >> >>
> >> >>
> >> >> However when I change the string as suggested on remus
pages to
> enable
> >> >> the
> >> >> disk replication its still failed :
> >> >>
> >> >> name = "DomU"
> >> >> memory = 1024
> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
> >> >> vif = [''ip=192.168.1.55,bridge=xenbr0'']
> >> >> bootloader = "pygrub"
> >> >>
> >> >> with error messages :
> >> >>
> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
> >> >> Using config file "/etc/xen/DomU.cfg".
> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
> >> >> failed
> >> >> (512  )
> >> >>
> >> >> and on the log file :
> >> >>
> >> >>
> >> >> name1@machine1:~$ sudo sudo tail /var/log/xen/xend.log
> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
> >> >>   File
> >> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
> >> >> line
> >> >> 3987, in create_vbd
> >> >>     devid = dev_control.createDevice(config)
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 174, in createDevice
> >> >>     device = TapdiskController.create(params, file)
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 286, in create
> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
> image))
> >> >>   File
> >> >>
> >> >>
>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
> >> >> line 233, in exc
> >> >>     (args, rc, out, err))
> >> >> TapdiskException: (''create'',
> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
> >> >>
> >> >> Any hints and help would very appreciated.
> >> >>
> >> >> Regards,
> >> >>
> >> >> Agya
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@lists.xen.org
> >> >> http://lists.xen.org/xen-devel
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Xen-devel mailing list
> >> > Xen-devel@lists.xen.org
> >> > http://lists.xen.org/xen-devel
> >> >
> >
> >
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

I forgot to told that its  work with protocol C

 $ sudo drbd-overview
  1:drbd-vm  SyncTarget Secondary/Secondary Inconsistent/UpToDate C r-----
        [=>..................] sync''ed: 12.0% (9016/10236)M

$ sudo drbd-overview
  1:drbd-vm  Connected Secondary/Secondary UpToDate/UpToDate C r-----


On Mon, Feb 18, 2013 at 11:00 PM, agya naila <agya.naila@gmail.com> wrote:
> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
>
>> Hi,
>>  I suggest you read up on the DRBD setup documentation from the
>> drbd.org website.
>>  The setup procedure is same. You can later flip to the remus
>> replication protocol by simply
>>  changing the protocol type (C to D).
>>
>> I am comparing my configuration with drbd website, however I got this
> error :
>
> $ sudo drbdadm up drbd-vm
> *''D'' is no valid protocol.*
> *Command ''drbdsetup 1 net ipv4:10.10.10.1:7789
ipv4:10.10.10.3:7789 D
> --set-defaults --create-device --rr-conflict=disconnect
> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
> --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4
> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
> --ping-timeout=20 --ping-int=3 --timeout=30'' terminated with exit
code 20*
> *drbdadm connect drbd-vm: exited with code 20*
> *
> *
> $ sudo drbd-overview
>   1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s
>
> Thank you,
>
> Agya
>
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila
<agya.naila@gmail.com> wrote:
>> >
>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <
>> rshriram@cs.ubc.ca>
>> > wrote:
>> >>
>> >> hi
>> >
>> >
>> > Thank you shriram.
>> >
>> >>
>> >>  sorry for the delayed response. IIRC the blktap2 driver
required for
>> >> tapdisk replication doesnt exist in the mainstream dom0
kernels, IIRC.
>> >>  I havent used it in a long time myself. I suggest trying disk
>> >> replication with DRBD.
>> >>
>> >
>> > I am also found some information here
>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2
>> problem on
>> > amd64 architecture. I have tried to install and configure the DRBD
but
>> its
>> > didn''t connect each other.
>> > I used drbd-8.3.11-remus and installed as follow
>> >
>> > cd /usr/src/
>> > wget
>> >
>>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
>> > tar xzf drbd-8.3.9-remus.tar.gz
>> > chown -R root:root drbd-8.3-remus
>> > cd /usr/src/drbd-8.3-remus
>> > chmod 777 autogen.sh
>> > ./autogen.sh
>> > dpkg-buildpackage -b -uc
>> > cd /usr/src/drbd-8.3-remus/drbd
>> > make clean
>> > make
>> > make install
>> > cd /usr/src/
>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
>> > /etc/drbd.d/global_common.conf
>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
>> > /etc/drbd.d/SystemHA_protoD.res
>> >
>> > sudo apt-get install drbd8-utils
>> >
>> >  from tutorial
>> http://remusha.wikidot.com/configuring-and-installing-remus
>> >
>> > My *.res configuration as follow :
>> >
>> > resource drbd-vm{
>> >   device    /dev/drbd1;
>> >   disk      /dev/vgvoip/DomU;
>> >   meta-disk internal;
>> >   on machine1 {
>> >     address   10.10.10.1:7789;
>> >   }
>> >   on machine2 {
>> >     address   10.10.10.3:7789;
>> >   }
>> > }
>> >
>> > and then I invoke command to create that meta
>> >
>> > drbdadm create-md drbd-vm
>> >
>> > However, when I try to make this configuration up by :
>> >
>> > drbdadm up drbd-vm
>> >
>> > Its come with error :
>> >
>> > $ sudo drbdadm up drbd-vm
>> > 1: Failure: (124) Device is attached to a disk (use detach first)
>> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU
/dev/vgvoip/DomU internal
>> > --set-defaults --create-device --fencing=dont-care
>> --on-io-error=pass_on''
>> > terminated with exit code 10
>> >
>> > If I run the
>> >
>> > $ sudo drbdadm detach drbd-vm
>> >
>> > Its come error
>> >
>> > $ sudo drbdadm detach drbd-vm
>> > 1: State change failed: (-2) Need access to UpToDate data
>> > Command ''drbdsetup 1 detach'' terminated with
exit code 17
>> >
>> > Here the /proc/drbd on both machine
>> >
>> > Machine 1
>> >
>> > $ sudo cat /proc/drbd
>> > version: 8.3.11 (api:88/proto:86-96)
>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>> root@machine1,
>> > 2013-02-18 18:49:57
>> >
>> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
>> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
>> > chkpt:0 oos:10485404
>> >
>> >
>> > Machine 2
>> >
>> > $ sudo cat /proc/drbd
>> > version: 8.3.11 (api:88/proto:86-96)
>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>> root@machine2,
>> > 2013-02-18 19:26:57
>> >
>> >  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown  
r----s
>> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
>> > chkpt:0 oos:10485404
>> >
>> >
>> > Do you have some hints?
>> >
>> > Thank you,
>> >
>> >
>> > Agya
>> >
>> >
>> >> thanks
>> >> shriram
>> >>
>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <
>> herydians@gmail.com>
>> >> wrote:
>> >> > Hello, Anyone have a clue? I have tried but still failed
:(
>> >> >
>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Dear all,
>> >> >>
>> >> >> I am configure my machine to run the remus disk
replication. I am
>> using
>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64
bit both for
>> Dom0
>> >> >> and
>> >> >> DomU.
>> >> >> I have install the blktap and its work properly with
configuration
>> >> >> string
>> >> >> phy or tap2 like this :
>> >> >> disk =
[''phy:/dev/vggroup/DomU,xvda,w'']
>> >> >> or
>> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>> >> >>
>> >> >> and remus command
>> >> >>
>> >> >> remus --no-net myvm mybackuphost
>> >> >>
>> >> >>
>> >> >> However when I change the string as suggested on
remus pages to
>> enable
>> >> >> the
>> >> >> disk replication its still failed :
>> >> >>
>> >> >> name = "DomU"
>> >> >> memory = 1024
>> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> >> >> vif =
[''ip=192.168.1.55,bridge=xenbr0'']
>> >> >> bootloader = "pygrub"
>> >> >>
>> >> >> with error messages :
>> >> >>
>> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> >> Using config file "/etc/xen/DomU.cfg".
>> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>> >> >> failed
>> >> >> (512  )
>> >> >>
>> >> >> and on the log file :
>> >> >>
>> >> >>
>> >> >> name1@machine1:~$ sudo sudo tail
/var/log/xen/xend.log
>> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>> >> >>   File
>> >> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>> >> >> line
>> >> >> 3987, in create_vbd
>> >> >>     devid = dev_control.createDevice(config)
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 174, in createDevice
>> >> >>     device = TapdiskController.create(params, file)
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 286, in create
>> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
>> image))
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 233, in exc
>> >> >>     (args, rc, out, err))
>> >> >> TapdiskException: (''create'',
>> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>> >> >>
>> >> >> Any hints and help would very appreciated.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Agya
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Xen-devel mailing list
>> >> >> Xen-devel@lists.xen.org
>> >> >> http://lists.xen.org/xen-devel
>> >> >>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Xen-devel mailing list
>> >> > Xen-devel@lists.xen.org
>> >> > http://lists.xen.org/xen-devel
>> >> >
>> >
>> >
>>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

I forgot to told that its  work with protocol C

 $ sudo drbd-overview
  1:drbd-vm  SyncTarget Secondary/Secondary Inconsistent/UpToDate C r-----
        [=>..................] sync''ed: 12.0% (9016/10236)M

$ sudo drbd-overview
  1:drbd-vm  Connected Secondary/Secondary UpToDate/UpToDate C r-----


On Mon, Feb 18, 2013 at 11:00 PM, agya naila <agya.naila@gmail.com> wrote:
> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca>wrote:
>
>> Hi,
>>  I suggest you read up on the DRBD setup documentation from the
>> drbd.org website.
>>  The setup procedure is same. You can later flip to the remus
>> replication protocol by simply
>>  changing the protocol type (C to D).
>>
>> I am comparing my configuration with drbd website, however I got this
> error :
>
> $ sudo drbdadm up drbd-vm
> *''D'' is no valid protocol.*
> *Command ''drbdsetup 1 net ipv4:10.10.10.1:7789
ipv4:10.10.10.3:7789 D
> --set-defaults --create-device --rr-conflict=disconnect
> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
> --after-sb-0pri=discard-younger-primary --allow-two-primaries --ko-count=4
> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
> --ping-timeout=20 --ping-int=3 --timeout=30'' terminated with exit
code 20*
> *drbdadm connect drbd-vm: exited with code 20*
> *
> *
> $ sudo drbd-overview
>   1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s
>
> Thank you,
>
> Agya
>
>
>
>> thanks
>> shriram
>>
>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila
<agya.naila@gmail.com> wrote:
>> >
>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <
>> rshriram@cs.ubc.ca>
>> > wrote:
>> >>
>> >> hi
>> >
>> >
>> > Thank you shriram.
>> >
>> >>
>> >>  sorry for the delayed response. IIRC the blktap2 driver
required for
>> >> tapdisk replication doesnt exist in the mainstream dom0
kernels, IIRC.
>> >>  I havent used it in a long time myself. I suggest trying disk
>> >> replication with DRBD.
>> >>
>> >
>> > I am also found some information here
>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about blktap2
>> problem on
>> > amd64 architecture. I have tried to install and configure the DRBD
but
>> its
>> > didn''t connect each other.
>> > I used drbd-8.3.11-remus and installed as follow
>> >
>> > cd /usr/src/
>> > wget
>> >
>>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
>> > tar xzf drbd-8.3.9-remus.tar.gz
>> > chown -R root:root drbd-8.3-remus
>> > cd /usr/src/drbd-8.3-remus
>> > chmod 777 autogen.sh
>> > ./autogen.sh
>> > dpkg-buildpackage -b -uc
>> > cd /usr/src/drbd-8.3-remus/drbd
>> > make clean
>> > make
>> > make install
>> > cd /usr/src/
>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
>> > /etc/drbd.d/global_common.conf
>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
>> > /etc/drbd.d/SystemHA_protoD.res
>> >
>> > sudo apt-get install drbd8-utils
>> >
>> >  from tutorial
>> http://remusha.wikidot.com/configuring-and-installing-remus
>> >
>> > My *.res configuration as follow :
>> >
>> > resource drbd-vm{
>> >   device    /dev/drbd1;
>> >   disk      /dev/vgvoip/DomU;
>> >   meta-disk internal;
>> >   on machine1 {
>> >     address   10.10.10.1:7789;
>> >   }
>> >   on machine2 {
>> >     address   10.10.10.3:7789;
>> >   }
>> > }
>> >
>> > and then I invoke command to create that meta
>> >
>> > drbdadm create-md drbd-vm
>> >
>> > However, when I try to make this configuration up by :
>> >
>> > drbdadm up drbd-vm
>> >
>> > Its come with error :
>> >
>> > $ sudo drbdadm up drbd-vm
>> > 1: Failure: (124) Device is attached to a disk (use detach first)
>> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU
/dev/vgvoip/DomU internal
>> > --set-defaults --create-device --fencing=dont-care
>> --on-io-error=pass_on''
>> > terminated with exit code 10
>> >
>> > If I run the
>> >
>> > $ sudo drbdadm detach drbd-vm
>> >
>> > Its come error
>> >
>> > $ sudo drbdadm detach drbd-vm
>> > 1: State change failed: (-2) Need access to UpToDate data
>> > Command ''drbdsetup 1 detach'' terminated with
exit code 17
>> >
>> > Here the /proc/drbd on both machine
>> >
>> > Machine 1
>> >
>> > $ sudo cat /proc/drbd
>> > version: 8.3.11 (api:88/proto:86-96)
>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>> root@machine1,
>> > 2013-02-18 18:49:57
>> >
>> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown   r----s
>> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
>> > chkpt:0 oos:10485404
>> >
>> >
>> > Machine 2
>> >
>> > $ sudo cat /proc/drbd
>> > version: 8.3.11 (api:88/proto:86-96)
>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>> root@machine2,
>> > 2013-02-18 19:26:57
>> >
>> >  1: cs:StandAlone ro:Secondary/Unknown ds:Inconsistent/DUnknown  
r----s
>> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
def:0
>> > chkpt:0 oos:10485404
>> >
>> >
>> > Do you have some hints?
>> >
>> > Thank you,
>> >
>> >
>> > Agya
>> >
>> >
>> >> thanks
>> >> shriram
>> >>
>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <
>> herydians@gmail.com>
>> >> wrote:
>> >> > Hello, Anyone have a clue? I have tried but still failed
:(
>> >> >
>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Dear all,
>> >> >>
>> >> >> I am configure my machine to run the remus disk
replication. I am
>> using
>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04 64
bit both for
>> Dom0
>> >> >> and
>> >> >> DomU.
>> >> >> I have install the blktap and its work properly with
configuration
>> >> >> string
>> >> >> phy or tap2 like this :
>> >> >> disk =
[''phy:/dev/vggroup/DomU,xvda,w'']
>> >> >> or
>> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>> >> >>
>> >> >> and remus command
>> >> >>
>> >> >> remus --no-net myvm mybackuphost
>> >> >>
>> >> >>
>> >> >> However when I change the string as suggested on
remus pages to
>> enable
>> >> >> the
>> >> >> disk replication its still failed :
>> >> >>
>> >> >> name = "DomU"
>> >> >> memory = 1024
>> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>> >> >> vif =
[''ip=192.168.1.55,bridge=xenbr0'']
>> >> >> bootloader = "pygrub"
>> >> >>
>> >> >> with error messages :
>> >> >>
>> >> >> name1@machine1:~$ sudo xm create -c /etc/xen/DomU.cfg
>> >> >> Using config file "/etc/xen/DomU.cfg".
>> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>> >> >> failed
>> >> >> (512  )
>> >> >>
>> >> >> and on the log file :
>> >> >>
>> >> >>
>> >> >> name1@machine1:~$ sudo sudo tail
/var/log/xen/xend.log
>> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd, disk);
>> >> >>   File
>> >> >>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>> >> >> line
>> >> >> 3987, in create_vbd
>> >> >>     devid = dev_control.createDevice(config)
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 174, in createDevice
>> >> >>     device = TapdiskController.create(params, file)
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 286, in create
>> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
>> image))
>> >> >>   File
>> >> >>
>> >> >>
>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>> >> >> line 233, in exc
>> >> >>     (args, rc, out, err))
>> >> >> TapdiskException: (''create'',
>> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>> >> >>
>> >> >> Any hints and help would very appreciated.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Agya
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> Xen-devel mailing list
>> >> >> Xen-devel@lists.xen.org
>> >> >> http://lists.xen.org/xen-devel
>> >> >>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Xen-devel mailing list
>> >> > Xen-devel@lists.xen.org
>> >> > http://lists.xen.org/xen-devel
>> >> >
>> >
>> >
>>
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Okay, I solve it. I removed drbd8-utils and re-install drbd from sources.
DRBD connected with D protocol. I could go further with disk replication,
hopefully there is no mistaken step again :)

Regards,

Agya

On Mon, Feb 18, 2013 at 11:13 PM, agya naila <agya.naila@gmail.com> wrote:
> I forgot to told that its  work with protocol C
>
>  $ sudo drbd-overview
>   1:drbd-vm  SyncTarget Secondary/Secondary Inconsistent/UpToDate C r-----
>         [=>..................] sync''ed: 12.0% (9016/10236)M
>
> $ sudo drbd-overview
>   1:drbd-vm  Connected Secondary/Secondary UpToDate/UpToDate C r-----
>
>
> On Mon, Feb 18, 2013 at 11:00 PM, agya naila <agya.naila@gmail.com>
wrote:
>
>> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca
>> > wrote:
>>
>>> Hi,
>>>  I suggest you read up on the DRBD setup documentation from the
>>> drbd.org website.
>>>  The setup procedure is same. You can later flip to the remus
>>> replication protocol by simply
>>>  changing the protocol type (C to D).
>>>
>>> I am comparing my configuration with drbd website, however I got
this
>> error :
>>
>> $ sudo drbdadm up drbd-vm
>> *''D'' is no valid protocol.*
>> *Command ''drbdsetup 1 net ipv4:10.10.10.1:7789
ipv4:10.10.10.3:7789 D
>> --set-defaults --create-device --rr-conflict=disconnect
>> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
>> --after-sb-0pri=discard-younger-primary --allow-two-primaries
--ko-count=4
>> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
>> --ping-timeout=20 --ping-int=3 --timeout=30'' terminated with
exit code 20
>> *
>> *drbdadm connect drbd-vm: exited with code 20*
>> *
>> *
>> $ sudo drbd-overview
>>   1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s
>>
>> Thank you,
>>
>> Agya
>>
>>
>>
>>> thanks
>>> shriram
>>>
>>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila
<agya.naila@gmail.com>
>>> wrote:
>>> >
>>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <
>>> rshriram@cs.ubc.ca>
>>> > wrote:
>>> >>
>>> >> hi
>>> >
>>> >
>>> > Thank you shriram.
>>> >
>>> >>
>>> >>  sorry for the delayed response. IIRC the blktap2 driver
required for
>>> >> tapdisk replication doesnt exist in the mainstream dom0
kernels, IIRC.
>>> >>  I havent used it in a long time myself. I suggest trying
disk
>>> >> replication with DRBD.
>>> >>
>>> >
>>> > I am also found some information here
>>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about
blktap2
>>> problem on
>>> > amd64 architecture. I have tried to install and configure the
DRBD but
>>> its
>>> > didn''t connect each other.
>>> > I used drbd-8.3.11-remus and installed as follow
>>> >
>>> > cd /usr/src/
>>> > wget
>>> >
>>>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
>>> > tar xzf drbd-8.3.9-remus.tar.gz
>>> > chown -R root:root drbd-8.3-remus
>>> > cd /usr/src/drbd-8.3-remus
>>> > chmod 777 autogen.sh
>>> > ./autogen.sh
>>> > dpkg-buildpackage -b -uc
>>> > cd /usr/src/drbd-8.3-remus/drbd
>>> > make clean
>>> > make
>>> > make install
>>> > cd /usr/src/
>>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
>>> > /etc/drbd.d/global_common.conf
>>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
>>> > /etc/drbd.d/SystemHA_protoD.res
>>> >
>>> > sudo apt-get install drbd8-utils
>>> >
>>> >  from tutorial
>>> http://remusha.wikidot.com/configuring-and-installing-remus
>>> >
>>> > My *.res configuration as follow :
>>> >
>>> > resource drbd-vm{
>>> >   device    /dev/drbd1;
>>> >   disk      /dev/vgvoip/DomU;
>>> >   meta-disk internal;
>>> >   on machine1 {
>>> >     address   10.10.10.1:7789;
>>> >   }
>>> >   on machine2 {
>>> >     address   10.10.10.3:7789;
>>> >   }
>>> > }
>>> >
>>> > and then I invoke command to create that meta
>>> >
>>> > drbdadm create-md drbd-vm
>>> >
>>> > However, when I try to make this configuration up by :
>>> >
>>> > drbdadm up drbd-vm
>>> >
>>> > Its come with error :
>>> >
>>> > $ sudo drbdadm up drbd-vm
>>> > 1: Failure: (124) Device is attached to a disk (use detach
first)
>>> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU
/dev/vgvoip/DomU internal
>>> > --set-defaults --create-device --fencing=dont-care
>>> --on-io-error=pass_on''
>>> > terminated with exit code 10
>>> >
>>> > If I run the
>>> >
>>> > $ sudo drbdadm detach drbd-vm
>>> >
>>> > Its come error
>>> >
>>> > $ sudo drbdadm detach drbd-vm
>>> > 1: State change failed: (-2) Need access to UpToDate data
>>> > Command ''drbdsetup 1 detach'' terminated with
exit code 17
>>> >
>>> > Here the /proc/drbd on both machine
>>> >
>>> > Machine 1
>>> >
>>> > $ sudo cat /proc/drbd
>>> > version: 8.3.11 (api:88/proto:86-96)
>>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>>> root@machine1,
>>> > 2013-02-18 18:49:57
>>> >
>>> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown  
r----s
>>> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b
>>> def:0
>>> > chkpt:0 oos:10485404
>>> >
>>> >
>>> > Machine 2
>>> >
>>> > $ sudo cat /proc/drbd
>>> > version: 8.3.11 (api:88/proto:86-96)
>>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>>> root@machine2,
>>> > 2013-02-18 19:26:57
>>> >
>>> >  1: cs:StandAlone ro:Secondary/Unknown
ds:Inconsistent/DUnknown
>>> r----s
>>> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b def:0
>>> > chkpt:0 oos:10485404
>>> >
>>> >
>>> > Do you have some hints?
>>> >
>>> > Thank you,
>>> >
>>> >
>>> > Agya
>>> >
>>> >
>>> >> thanks
>>> >> shriram
>>> >>
>>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <
>>> herydians@gmail.com>
>>> >> wrote:
>>> >> > Hello, Anyone have a clue? I have tried but still
failed :(
>>> >> >
>>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> Dear all,
>>> >> >>
>>> >> >> I am configure my machine to run the remus disk
replication. I am
>>> using
>>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04
64 bit both for
>>> Dom0
>>> >> >> and
>>> >> >> DomU.
>>> >> >> I have install the blktap and its work properly
with configuration
>>> >> >> string
>>> >> >> phy or tap2 like this :
>>> >> >> disk =
[''phy:/dev/vggroup/DomU,xvda,w'']
>>> >> >> or
>>> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>>> >> >>
>>> >> >> and remus command
>>> >> >>
>>> >> >> remus --no-net myvm mybackuphost
>>> >> >>
>>> >> >>
>>> >> >> However when I change the string as suggested on
remus pages to
>>> enable
>>> >> >> the
>>> >> >> disk replication its still failed :
>>> >> >>
>>> >> >> name = "DomU"
>>> >> >> memory = 1024
>>> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>>> >> >> vif =
[''ip=192.168.1.55,bridge=xenbr0'']
>>> >> >> bootloader = "pygrub"
>>> >> >>
>>> >> >> with error messages :
>>> >> >>
>>> >> >> name1@machine1:~$ sudo xm create -c
/etc/xen/DomU.cfg
>>> >> >> Using config file "/etc/xen/DomU.cfg".
>>> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>>> >> >> failed
>>> >> >> (512  )
>>> >> >>
>>> >> >> and on the log file :
>>> >> >>
>>> >> >>
>>> >> >> name1@machine1:~$ sudo sudo tail
/var/log/xen/xend.log
>>> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd,
disk);
>>> >> >>   File
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>>> >> >> line
>>> >> >> 3987, in create_vbd
>>> >> >>     devid = dev_control.createDevice(config)
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 174, in createDevice
>>> >> >>     device = TapdiskController.create(params,
file)
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 286, in create
>>> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
>>> image))
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 233, in exc
>>> >> >>     (args, rc, out, err))
>>> >> >> TapdiskException: (''create'',
>>> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>>> >> >>
>>> >> >> Any hints and help would very appreciated.
>>> >> >>
>>> >> >> Regards,
>>> >> >>
>>> >> >> Agya
>>> >> >>
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >> Xen-devel mailing list
>>> >> >> Xen-devel@lists.xen.org
>>> >> >> http://lists.xen.org/xen-devel
>>> >> >>
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > Xen-devel mailing list
>>> >> > Xen-devel@lists.xen.org
>>> >> > http://lists.xen.org/xen-devel
>>> >> >
>>> >
>>> >
>>>
>>
>>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Okay, I solve it. I removed drbd8-utils and re-install drbd from sources.
DRBD connected with D protocol. I could go further with disk replication,
hopefully there is no mistaken step again :)

Regards,

Agya

On Mon, Feb 18, 2013 at 11:13 PM, agya naila <agya.naila@gmail.com> wrote:
> I forgot to told that its  work with protocol C
>
>  $ sudo drbd-overview
>   1:drbd-vm  SyncTarget Secondary/Secondary Inconsistent/UpToDate C r-----
>         [=>..................] sync''ed: 12.0% (9016/10236)M
>
> $ sudo drbd-overview
>   1:drbd-vm  Connected Secondary/Secondary UpToDate/UpToDate C r-----
>
>
> On Mon, Feb 18, 2013 at 11:00 PM, agya naila <agya.naila@gmail.com>
wrote:
>
>> On Mon, Feb 18, 2013 at 10:33 PM, Shriram Rajagopalan
<rshriram@cs.ubc.ca
>> > wrote:
>>
>>> Hi,
>>>  I suggest you read up on the DRBD setup documentation from the
>>> drbd.org website.
>>>  The setup procedure is same. You can later flip to the remus
>>> replication protocol by simply
>>>  changing the protocol type (C to D).
>>>
>>> I am comparing my configuration with drbd website, however I got
this
>> error :
>>
>> $ sudo drbdadm up drbd-vm
>> *''D'' is no valid protocol.*
>> *Command ''drbdsetup 1 net ipv4:10.10.10.1:7789
ipv4:10.10.10.3:7789 D
>> --set-defaults --create-device --rr-conflict=disconnect
>> --after-sb-2pri=disconnect --after-sb-1pri=discard-secondary
>> --after-sb-0pri=discard-younger-primary --allow-two-primaries
--ko-count=4
>> --max-epoch-size=4096 --unplug-watermark=4096 --max-buffers=8192
>> --ping-timeout=20 --ping-int=3 --timeout=30'' terminated with
exit code 20
>> *
>> *drbdadm connect drbd-vm: exited with code 20*
>> *
>> *
>> $ sudo drbd-overview
>>   1:drbd-vm  StandAlone Secondary/Unknown UpToDate/DUnknown r----s
>>
>> Thank you,
>>
>> Agya
>>
>>
>>
>>> thanks
>>> shriram
>>>
>>> On Mon, Feb 18, 2013 at 4:11 PM, agya naila
<agya.naila@gmail.com>
>>> wrote:
>>> >
>>> > On Mon, Feb 18, 2013 at 9:08 PM, Shriram Rajagopalan <
>>> rshriram@cs.ubc.ca>
>>> > wrote:
>>> >>
>>> >> hi
>>> >
>>> >
>>> > Thank you shriram.
>>> >
>>> >>
>>> >>  sorry for the delayed response. IIRC the blktap2 driver
required for
>>> >> tapdisk replication doesnt exist in the mainstream dom0
kernels, IIRC.
>>> >>  I havent used it in a long time myself. I suggest trying
disk
>>> >> replication with DRBD.
>>> >>
>>> >
>>> > I am also found some information here
>>> > http://osdir.com/ml/xen-users/2011-07/msg00653.html about
blktap2
>>> problem on
>>> > amd64 architecture. I have tried to install and configure the
DRBD but
>>> its
>>> > didn''t connect each other.
>>> > I used drbd-8.3.11-remus and installed as follow
>>> >
>>> > cd /usr/src/
>>> > wget
>>> >
>>>
http://remusha.wikidot.com/local--files/configuring-and-installing-remus/drbd-8.3.11-remus.tar.gz
>>> > tar xzf drbd-8.3.9-remus.tar.gz
>>> > chown -R root:root drbd-8.3-remus
>>> > cd /usr/src/drbd-8.3-remus
>>> > chmod 777 autogen.sh
>>> > ./autogen.sh
>>> > dpkg-buildpackage -b -uc
>>> > cd /usr/src/drbd-8.3-remus/drbd
>>> > make clean
>>> > make
>>> > make install
>>> > cd /usr/src/
>>> > cp /usr/src/drbd-8.3-remus/scripts/global_common.conf.protoD
>>> > /etc/drbd.d/global_common.conf
>>> > cp /usr/src/drbd-8.3-remus/scripts/testvms_protoD.res
>>> > /etc/drbd.d/SystemHA_protoD.res
>>> >
>>> > sudo apt-get install drbd8-utils
>>> >
>>> >  from tutorial
>>> http://remusha.wikidot.com/configuring-and-installing-remus
>>> >
>>> > My *.res configuration as follow :
>>> >
>>> > resource drbd-vm{
>>> >   device    /dev/drbd1;
>>> >   disk      /dev/vgvoip/DomU;
>>> >   meta-disk internal;
>>> >   on machine1 {
>>> >     address   10.10.10.1:7789;
>>> >   }
>>> >   on machine2 {
>>> >     address   10.10.10.3:7789;
>>> >   }
>>> > }
>>> >
>>> > and then I invoke command to create that meta
>>> >
>>> > drbdadm create-md drbd-vm
>>> >
>>> > However, when I try to make this configuration up by :
>>> >
>>> > drbdadm up drbd-vm
>>> >
>>> > Its come with error :
>>> >
>>> > $ sudo drbdadm up drbd-vm
>>> > 1: Failure: (124) Device is attached to a disk (use detach
first)
>>> > Command ''drbdsetup 1 disk /dev/vgvoip/DomU
/dev/vgvoip/DomU internal
>>> > --set-defaults --create-device --fencing=dont-care
>>> --on-io-error=pass_on''
>>> > terminated with exit code 10
>>> >
>>> > If I run the
>>> >
>>> > $ sudo drbdadm detach drbd-vm
>>> >
>>> > Its come error
>>> >
>>> > $ sudo drbdadm detach drbd-vm
>>> > 1: State change failed: (-2) Need access to UpToDate data
>>> > Command ''drbdsetup 1 detach'' terminated with
exit code 17
>>> >
>>> > Here the /proc/drbd on both machine
>>> >
>>> > Machine 1
>>> >
>>> > $ sudo cat /proc/drbd
>>> > version: 8.3.11 (api:88/proto:86-96)
>>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>>> root@machine1,
>>> > 2013-02-18 18:49:57
>>> >
>>> >  1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown  
r----s
>>> >     ns:0 nr:0 dw:0 dr:1712 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b
>>> def:0
>>> > chkpt:0 oos:10485404
>>> >
>>> >
>>> > Machine 2
>>> >
>>> > $ sudo cat /proc/drbd
>>> > version: 8.3.11 (api:88/proto:86-96)
>>> > GIT-hash: 0de839cee13a4160eed6037c4bddd066645e23c5 build by
>>> root@machine2,
>>> > 2013-02-18 19:26:57
>>> >
>>> >  1: cs:StandAlone ro:Secondary/Unknown
ds:Inconsistent/DUnknown
>>> r----s
>>> >     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b def:0
>>> > chkpt:0 oos:10485404
>>> >
>>> >
>>> > Do you have some hints?
>>> >
>>> > Thank you,
>>> >
>>> >
>>> > Agya
>>> >
>>> >
>>> >> thanks
>>> >> shriram
>>> >>
>>> >> On Mon, Feb 18, 2013 at 5:38 AM, Hery Dian Septama <
>>> herydians@gmail.com>
>>> >> wrote:
>>> >> > Hello, Anyone have a clue? I have tried but still
failed :(
>>> >> >
>>> >> > On Sat, Feb 16, 2013 at 6:56 PM, agya naila
<agya.naila@gmail.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> Dear all,
>>> >> >>
>>> >> >> I am configure my machine to run the remus disk
replication. I am
>>> using
>>> >> >> xen 4.2.3 installed from sources and Ubuntu 12.04
64 bit both for
>>> Dom0
>>> >> >> and
>>> >> >> DomU.
>>> >> >> I have install the blktap and its work properly
with configuration
>>> >> >> string
>>> >> >> phy or tap2 like this :
>>> >> >> disk =
[''phy:/dev/vggroup/DomU,xvda,w'']
>>> >> >> or
>>> >> >> disk =
[''tap2:tapdisk:aio:/dev/vggroup/DomU,xvda,w'']
>>> >> >>
>>> >> >> and remus command
>>> >> >>
>>> >> >> remus --no-net myvm mybackuphost
>>> >> >>
>>> >> >>
>>> >> >> However when I change the string as suggested on
remus pages to
>>> enable
>>> >> >> the
>>> >> >> disk replication its still failed :
>>> >> >>
>>> >> >> name = "DomU"
>>> >> >> memory = 1024
>>> >> >> disk =
[''tap2:remus:10.10.10.3:8002|aio:/dev/vggroup/DomU,xvda,w'']
>>> >> >> vif =
[''ip=192.168.1.55,bridge=xenbr0'']
>>> >> >> bootloader = "pygrub"
>>> >> >>
>>> >> >> with error messages :
>>> >> >>
>>> >> >> name1@machine1:~$ sudo xm create -c
/etc/xen/DomU.cfg
>>> >> >> Using config file "/etc/xen/DomU.cfg".
>>> >> >> Error: (''create'',
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'')
>>> >> >> failed
>>> >> >> (512  )
>>> >> >>
>>> >> >> and on the log file :
>>> >> >>
>>> >> >>
>>> >> >> name1@machine1:~$ sudo sudo tail
/var/log/xen/xend.log
>>> >> >>     mounted_vbd_uuid = dom0.create_vbd(vbd,
disk);
>>> >> >>   File
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/XendDomainInfo.py",
>>> >> >> line
>>> >> >> 3987, in create_vbd
>>> >> >>     devid = dev_control.createDevice(config)
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 174, in createDevice
>>> >> >>     device = TapdiskController.create(params,
file)
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 286, in create
>>> >> >>     return
TapdiskController.exc(''create'', ''-a%s:%s'' %
(dtype,
>>> image))
>>> >> >>   File
>>> >> >>
>>> >> >>
>>>
"/usr/local/lib/python2.7/dist-packages/xen/xend/server/BlktapController.py",
>>> >> >> line 233, in exc
>>> >> >>     (args, rc, out, err))
>>> >> >> TapdiskException: (''create'',
>>> >> >>
''-aremus:10.10.10.3:8002|aio:/dev/vggroup/DomU'') failed (512 
)
>>> >> >>
>>> >> >> Any hints and help would very appreciated.
>>> >> >>
>>> >> >> Regards,
>>> >> >>
>>> >> >> Agya
>>> >> >>
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >> Xen-devel mailing list
>>> >> >> Xen-devel@lists.xen.org
>>> >> >> http://lists.xen.org/xen-devel
>>> >> >>
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > Xen-devel mailing list
>>> >> > Xen-devel@lists.xen.org
>>> >> > http://lists.xen.org/xen-devel
>>> >> >
>>> >
>>> >
>>>
>>
>>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users