> The concurrent verify fails/is not started because there is already one
> in progress.
Perfect! THX for clarification.
BR,
Jasmin
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
Il 04/01/2017 13:51, Roland Kammerer ha scritto:
> If you are a
> company and you provide commercial support/commercial trainings and make
> money out of that support business, then I think it is fair to give back
> a bit to the people that wrote the stuff you are making money with.
I agree, here
Il 04/01/2017 12:42, Igor Cicimov ha scritto:
> For the "has to remove [...] completely": Puh, dangerous territory to
> comment on, but that was the decision of Proxmox.
>
>
> No serious company would integrate drbd in their product and then tell
> their customers to talk to Linbit in ca
On Fri, Jan 06, 2017 at 06:32:34PM +0800, Jasmin J. wrote:
> Hi!
>
> I am using DRBD 8.4 in a two server configuration and I discovered that using
> drbdadm verify r0
> on the side witch is secondary, will also start a verify.
>
> The manual states, that you should add
> 42 0 * * 0root
Hi!
I am using DRBD 8.4 in a two server configuration and I discovered that using
drbdadm verify r0
on the side witch is secondary, will also start a verify.
The manual states, that you should add
42 0 * * 0root/sbin/drbdadm verify all
to the crontab to automate this.
If this is done
