Tinkering with timeouts could be risky, so in case you can't have a second
switch - your solution (shutting down all VMs, maintenance, etc) should be the
safest.
If possible test it on a cluster on VMs, so you get used to the whole procedure.
Best Regards,Strahil Nikolov
On Wed, Sep 29, 20
On 29. 09. 21 13:31, Vojtech Juranek wrote:
this is possible, but changing sanlock timeouts can be very tricky and can
have unwanted/unexpected consequences, so be very careful. Here is a guideline
how to do it:
https://github.com/oVirt/vdsm/blob/master/doc/io-timeouts.md
Thank you for your fe
On Wednesday, 29 September 2021 09:43:56 CEST cen wrote:
> Hi,
>
> we are experiencing a weird issue with our Ovirt setup. We have two
> physical hosts (DC1 and DC2) and mounted Lenovo NAS storage for all VM
> data.
> They are connected via a managed network switch.
>
> What happens is that if
On Wed, Sep 29, 2021 at 2:08 PM cen wrote:
>
> Hi,
>
> we are experiencing a weird issue with our Ovirt setup. We have two
> physical hosts (DC1 and DC2) and mounted Lenovo NAS storage for all VM data.
>
> They are connected via a managed network switch.
>
> What happens is that if switch goes dow
4 matches
Mail list logo
