with a large send buffer) as I need
to be 100% sure it will not crash the filesystem if protocol A is used. So far,
so good.
Thanks,
Ondrej
-Original Message-
From: Veit Wahlich [mailto:cru.li...@zodia.de]
Sent: Thursday, March 15, 2018 7:38 PM
To: drbd-user@lists.linbit.com; Ondrej Valousek
> That is perfectly expected behavior. Imagine a resync from the primary that,
> for some time, makes the secondary inconsistent (see what Lars already told
> you). Would not make sense to mount that
> one... Error codes are limited, "Wrong medium type" is the one that makes
> most sense.
>
Hi list,
When trying to mount the filesystem on the slave node (read-only, I do not want
to crash the filesystem), I am receiving:
mount: mount /dev/drbd0 on /brick1 failed: Wrong medium type
Is it normal? AFAIK it should be OK to mount the filesystem read-only on the
slave node.
Thanks,
---
From: drbd-user-boun...@lists.linbit.com
[mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of Lars Ellenberg
Sent: Wednesday, March 14, 2018 2:03 PM
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] Data consistency question
On Tue, Mar 13, 2018 at 10:23:25AM +, Ondrej Valousek wrote:
> Hi l
Hi list,
I have a question regarding filesystem consistency - say I choose async
protocol (A) and the master peer node crashes fatally in the middle of write
operation.
The slave peer node will then be outdated, but what happens to the filesystem
on the top of the replicated block device -
