Date: Thu, 21 Sep 2017 14:04:08 +0200 From: rainer@ultra-secure.de To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, freebsd-xen@freebsd.org, owner-freebsd-xen@freebsd.org Subject: Re: Storage 'failover' largely kills FreeBSD 10.x under XenServer? Message-ID: <5afd1ad53171583603bb8518dfbdd51b@ultra-secure.de> In-Reply-To: <1913BD3E6623F2384770C39E@[10.12.30.106]> References: <201709201815.v8KIF7Gi089958@pdx.rh.CN85.dnsmgr.net> <1913BD3E6623F2384770C39E@[10.12.30.106]>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 2017-09-21 13:33, schrieb Karl Pielorz: > --On 20 September 2017 11:15 -0700 "Rodney W. Grimes" > <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> wrote: > >> As you found one of these let me point out the pair of them: >> kern.cam.ada.default_timeout: 30 >> kern.cam.ada.retry_count: 4 > > Adjusting these doesn't seem to make any difference at all. I asked myself already if the disks from Xen(Server) are really CAM-disks. They certainly don't show up with camcontrol devlist. If they don't show-up there, why should any cam timeouts apply? BTW: storage-failures also kill various Linux hosts. They usually turn their filesystem into read-only mode and then you've got to reboot anyway.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5afd1ad53171583603bb8518dfbdd51b>