> -Original Message-
> From: Users On Behalf Of Ulrich Windl
> Sent: Tuesday, May 18, 2021 12:51 AM
> To: users@clusterlabs.org
> Subject: [ClusterLabs] Antw: [EXT] Re: DRBD + VDO HowTo?
>
> >>> Eric Robinson schrieb am 17.05.2021 um
> 20:28 in
> Nachricht
> 03.prod.outlook.com>
> >
>>> Eric Robinson schrieb am 17.05.2021 um 20:28 in
Nachricht
> R=$(/usr/bin/vdo status -n $VOL|grep Activate|awk '{$1=$1};1'|cut
I just wonder: What is "awk '{$1=$1};1'" supposed to do?
I also believe that "grep Activate|awk '{$1=$1};1'|cut -d" " -f2)" can be done
in one awk command.
On 17.05.2021 21:28, Eric Robinson wrote:
> Andrei --
>
> Sorry for the novels. Sometimes it is hard to tell whether people want all
> the configs, logs, and scripts first, or if they want a description of the
> problem and what one is trying to accomplish first. I'll send whatever you
> want.
Okay, here is a test, starting with the initial cluster status...
[root@ha09a ~]# pcs status
Cluster name: ha09ab
Cluster Summary:
* Stack: corosync
* Current DC: ha09a (version 2.0.4-6.el8_3.2-2deceaa3ae) - partition with
quorum
* Last updated: Mon May 17 22:14:11 2021
* Last change: M
Notice in that 'pcs status' shows errors for resource p_vdo0 on node ha09b,
even after doing 'pcs resource cleanup p_vdo0'.
[root@ha09a ~]# pcs status
Cluster name: ha09ab
Cluster Summary:
* Stack: corosync
* Current DC: ha09a (version 2.0.4-6.el8_3.2-2deceaa3ae) - partition with
quorum
*
Andrei --
To follow up, here is the Pacemaker config. Let's not talk about fencing or
quorum right now. I want to focus on the vdo issue at hand.
[root@ha09a ~]# pcs config
Cluster Name: ha09ab
Corosync Nodes:
ha09a ha09b
Pacemaker Nodes:
ha09a ha09b
Resources:
Clone: p_drbd0-clone
Meta At
Andrei --
Sorry for the novels. Sometimes it is hard to tell whether people want all the
configs, logs, and scripts first, or if they want a description of the problem
and what one is trying to accomplish first. I'll send whatever you want. I am
very eager to get to the bottom of this.
I'll st
On 17.05.2021 18:18, Eric Robinson wrote:
> To Strahil and Klaus –
>
> I created the vdo devices using default parameters, so ‘auto’ mode was
> selected by default. vdostatus shows that the current mode is async. The
> underlying drbd devices are running protocol C, so I assume that vdo should
To Strahil and Klaus –
I created the vdo devices using default parameters, so ‘auto’ mode was selected
by default. vdostatus shows that the current mode is async. The underlying drbd
devices are running protocol C, so I assume that vdo should be changed to sync
mode?
The VDO service is disable
Have you tried to set VDO in async mode ?
Best Regards,Strahil Nikolov
On Mon, May 17, 2021 at 8:57, Klaus Wenninger wrote:
Did you try VDO in sync-mode for the case the flush-fua stuff isn't working
through the layers? Did you check that VDO-service is disabled and solely under
pacemak
10 matches
Mail list logo
