[DRBD-user] Receiving a message "disk size of peer is too small"

2017-09-12 Thread José Andrés Matamoros Guevara
I have two different servers with drbd replication. One disk failed in one of the servers. I have replaced it with a newer disk with physical sector size of 4096 bytes. The old one is 512 bytes. Now, I’m receiving a message saying “the disk size of peer is too small” and the resources don’t con

[DRBD-user] Promote client-only to complete node ?

2017-09-12 Thread Julien Escario
Hello, I'm trying to 'promote' a client node to have a local copy of datas but can't find any reference to such command in manual. I tried : vm-260-disk-1 role:Secondary disk:Diskless vm4 role:Secondary peer-disk:UpToDate vm5 role:Secondary peer-disk:UpToDate This one is in secondar

Re: [DRBD-user] Authentication of peer failed ?

2017-09-12 Thread Julien Escario
Le 12/09/2017 à 00:11, Lars Ellenberg a écrit : > On Mon, Sep 11, 2017 at 11:21:35AM +0200, Julien Escario wrote: >> Hello, >> This moring, when creating a ressource from Proxmox, I got a nice >> "Authentication of peer failed". >> >> [33685507.246574] drbd vm-115-disk-1 vm7: Handshake to peer 2 su

Re: [DRBD-user] Receiving a message "disk size of peer is too small"

2017-09-12 Thread Yannis Milios
On Tue, Sep 12, 2017 at 1:50 AM, José Andrés Matamoros Guevara < amatamo...@ie-networks.com> wrote: > I have two different servers with drbd replication. One disk failed in one > of the servers. I have replaced it with a newer disk with physical sector > size of 4096 bytes. The old one is 512 byte

Re: [DRBD-user] Promote client-only to complete node ?

2017-09-12 Thread Roland Kammerer
On Tue, Sep 12, 2017 at 09:49:26AM +0200, Julien Escario wrote: > Hello, > I'm trying to 'promote' a client node to have a local copy of datas but can't > find any reference to such command in manual. > > I tried : > vm-260-disk-1 role:Secondary > disk:Diskless > vm4 role:Secondary > peer-

Re: [DRBD-user] Receiving a message "disk size of peer is too small"

2017-09-12 Thread Yannis Milios
>The partition takes all the disk, but in the new one, when I created it, was a little smaller. That's the case then. What about leaving the new disk unpartitioned and using it as /dev/sdb (instead of /dev/sdb1) ? Otherwise I guess 2 options remain: - Buy a bigger disk - Shrink the original in o