On Mon, Feb 1, 2021 at 4:09 PM Nir Soffer <[email protected]> wrote: [snip]
> > The easiest way to get vdsm defaults is to change the the file to use > an older version, > (e.g. use 1.9), remove the private comment, and run: > > vdms-tool configure --force --module multipath > > Vdsm will upgrade your old file to the most recent version, and backup > your old file > to /etc/multipath.conf.timestamp. > thanks > For 120 seconds, you likey need > > sanlock:io_timeout=20 > no_path_retry=32 > > Shouldn't the above values for a 160 seconds timeout? I need 120 Because of the different way sanlock and multipath handles timeouts. > > Also note that our QE never tested changing these settings, but your > feedback on this new > configuration is very important. > ok > > multipath -r deleages the command to multipathd daemon, this is > probably the reason > you don't see the logs here. > > I think this will be more useful: > > multipathd reconfigure -v3 > > I'm not sure about the -v3, check multipathd manual for the details. > > Nir > > On another host with same config (other luns on the same storage), if I run: multipath reconfigure -v4 > /tmp/multipath_reconfigure_v4.txt 2>&1 I get this: https://drive.google.com/file/d/1VkezFkT9IwsrYD8LoIp4-Q-j2X1dN_qR/view?usp=sharing anything important inside, concerned with path retry settings?
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/FC5ZONSANUSXKJCYTPEOAWDLZOGDR7TF/
