Hi,
good news for the weekend, the next drbd-9 release will be ready
in one week.
Get your test equipment ready next week, and let us know if you
find anything suspicious.
This release will be very important for users that have diskless,
primary nodes in their setups.
drbd
9.0.9rc1-1
Hi Dirk,
this is most likely caused by a NIC model not supported by the guest OS'
drivers, but this is also totally off-topic redarding this is the DRBD
ML. I suggest you consult the KVM/qemu/libvirt MLs on this topic
instead.
Beste Gruesze,
// Veit
Am Freitag, den 04.08.2017, 13:59 +
Hello,
I exported one of my virtual maschines from Oracle virtualbox to ova 2.0 and
converted this file to KVM qcow2 like described for example in this tutorial:
https://utappia.org/2016/04/20/how-to-migrate-virtual-box-machines-to-the-kvm-virtmanager/
Unfortunatly this vm does not bring up
I set up 2-node NFS cluster on drbd 8.4 across two sites connected with
10GB link. I run MQ benchmark with result of 100 units which is poor. When
I disable drbd synchronizations I get 200 units which is good. That's twice
faster. Is it normal for drbd to slow down that much ?
Thank you
On Fri, Aug 04, 2017 at 10:31:02AM +0200, Jan Schermer wrote:
> I think it’s more likely he’s hitting a number of bugs that are
> getting fixed in DRBD, where it would simply not resync data while
> appearing Consistent/UpToDate etc.
No. This is a drbd8.4 setup and you are talking about drbd9.
AFAIK this should not affect data integrity at rest (related to “verify-alg”)
but only in-flight (csum-alg), and even then at most few blocks (that are
in-flight) should be affected? (btw shouldn’t stable_pages_required be enabled?)
I think it’s more likely he’s hitting a number of bugs that
Hi Luke,
I assume you are experiencing the results of data inconsistency by
in-flight writes. This means that a process (here your VM's qemu) can
change a block that already waits to be written to disk.
Whether this happens (undetected) or not depends on how the data is
accessed for writing and
On 03/08/17 17:38, Simon Ironside wrote:
> On 07/07/17 14:41, Lafaille Christophe wrote:
>
>> Today, I can't compile drbd 8.4.10-1 on my RHEL 7.4 Beta platform, an
>> error is returned...
>
> Same happens on RHEL 7.4 GA, released a couple of days ago, with their
> stock kernel package version
I upgraded one of my servers to RHEL7.4 yesterday. Because the kernel
changed, I needed to recompile DRBD. This failed.
After the first failure, I deleted my /usr/src/drbd-8.4 directory and
followed the "git download" instructions in the DRBD User's Guide to obtain
a fresh copy of drbd-8.4.10-1.
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual
machines, with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each,
totalling 47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's
own Gig-E
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual machines,
with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each, totalling
47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's own
Gig-E
Hello everyone.
I have a fairly simple 2-node CentOS 7 setup running KVM virtual machines,
with DRBD 8.4.9 between them.
There is one DRBD resource per VM, with at least 1 volume each, totalling
47 volumes.
There's no clustering or heartbeat or other complexity. DRBD has it's own
Gig-E
On Fri, Jul 07, 2017 at 03:41:32PM +0200, Lafaille Christophe wrote:
>Hi,
>
>I've downloaded RHEL7.4 Beta in order to prepare my future platform for
>drbd+corosync+pacemaker.
>
>Today, I can't compile drbd 8.4.10-1 on my RHEL 7.4 Beta platform, an
>error is returned...
>
>
13 matches
Mail list logo
