Re: [DRBD-user] how about read a block that not return to upper application in protocol C?

2016-09-05 Thread Lars Ellenberg
On Mon, Sep 05, 2016 at 01:16:21AM +0800, Mia Lueng wrote: > Hi All: > In protocol C, a bio will return to upper application(execute > bi_endio()) when local bio is completed and recieve the data ack > packet from peer. But if a write request to block N was submitted > and written to local

Re: [DRBD-user] Proxmox VE 4.2 and DRBD 9

2016-09-05 Thread Jean-Daniel TISSOT
Hi Robert, Thanks a lot. This export solve my problem. A drbdadm adjust all and after a drbdadm status show me good results. Le 05/09/2016 à 11:54, Robert Altnoeder a écrit : > On 09/02/2016 06:05 PM, Jean-Daniel TISSOT wrote: >> Hi list, >> >> I remark i have a file

Re: [DRBD-user] Proxmox VE 4.2 and DRBD 9

2016-09-05 Thread Robert Altnoeder
On 09/02/2016 06:05 PM, Jean-Daniel TISSOT wrote: > Hi list, > > I remark i have a file /var/lib/drbd.d/drbdmanage_vm-100-disk-2.res [...] > If i reboot a node, this file disappear on this node [...] > [...] if i do drbdadm connect vm-100-disk-2 i receive : > 'vm-100-disk-2' not defined in your

Re: [DRBD-user] How to solve split brain?

2016-09-05 Thread Michele Rossetti
On node 1: root@mpve1:~# drbdsetup status vm-100-disk-1 --verbose --statistics vm-100-disk-1 node-id:0 role:Secondary suspended:no write-ordering:flush volume:0 minor:100 disk:Inconsistent size:33554432 read:0 written:0 al-writes:0 bm-writes:0 upper-pending:0 lower-pending:0

Re: [DRBD-user] How to solve split brain?

2016-09-05 Thread Roberto Resoli
Il 05/09/2016 12:56, Michele Rossetti ha scritto: > On node 1: > root@mpve1:~# drbdsetup status vm-100-disk-1 --verbose --statistics > vm-100-disk-1 node-id:0 role:Secondary suspended:no > write-ordering:flush > volume:0 minor:100 disk:Inconsistent > size:33554432 read:0 written:0

Re: [DRBD-user] Proxmox VE 4.2 and DRBD 9

2016-09-05 Thread Jean-Daniel TISSOT
Hi again, In fact there is other problems, when I migrate a VM on another node, it's fail with this error message : sept. 05 16:26:32 starting migration of VM 100 to node 'dmz-pve2' (192.168.0.20) sept. 05 16:26:32 copying disk images sept. 05 16:26:32 starting VM 100 on remote node 'dmz-pve2'

Re: [DRBD-user] DRBD resource expansion trouble

2016-09-05 Thread Peter Brunnengraeber
Hello all, Thought I would provide an update as someone may find this useful. So I was able to resolve my situation. Here is what I did: - Changed drbd config to use the raw [/dev/sdc] device on the secondary node - Wiped out /dev/sdc on the secondary node [dd if=/dev/zero

Re: [DRBD-user] Proxmox VE 4.2 and DRBD 9

2016-09-05 Thread Igor Cicimov
On Tue, Sep 6, 2016 at 12:49 AM, Jean-Daniel TISSOT < jean-daniel.tis...@univ-fcomte.fr> wrote: > Hi again, > > In fact there is other problems, when I migrate a VM on another node, it's > fail with this error message : > > sept. 05 16:26:32 starting migration of VM 100 to node 'dmz-pve2' >

Re: [DRBD-user] How to solve split brain?

2016-09-05 Thread Roberto Resoli
Il 02/09/2016 18:10, Michele Rossetti ha scritto: > Hi All, > I don't know if I'm involved in a split brain situation on my new > Proxmox4 with DRBD9 3 nodes, this is the output of drbd-overview: > > root@mpve2:~# drbd-overview > 0:.drbdctrl/0 Connected(3*) Secondary(3*) >