On Tue, Nov 27, 2018 at 9:34 AM Sahina Bose wrote:
> On Tue, Nov 13, 2018 at 4:46 PM fsoyer wrote:
> 1, 'Read timeout') - indicates that there was no response from storage
> within 32s (I think this is the sanlock read timeout? Denis? Nir?)
>
This:
> 2018-11-11 14:33:49,450+0100 ERROR (check/l
Hi,
I can say now that the problem was related to storage performances, as there
was no more errors since the replacement of the raid cards.
Thanks for all,
Frank
Le Mardi, Novembre 27, 2018 08:30 CET, Sahina Bose a écrit:
On Tue, Nov 13, 2018 at 4:46 PM fsoyer wrote:
>
> Hi all,
> I contin
Hi,
questioning me about all the chain oVirt -> Gluster -> hardware, I continued to
check all the components, finally testing the hardware.
I found some latencies on storage when it was busy, and some searches on web
convinced me that the RAID cards could be the problem : Dell servers are
shipp
On Tue, Nov 13, 2018 at 4:46 PM fsoyer wrote:
>
> Hi all,
> I continue to try to understand my problem between (I suppose) oVirt anf
> Gluster.
> After my recents posts titled 'VMs unexpectidly restarted' that did not
> provide solution nor search idea, I submit to you another (related ?) proble
4 matches
Mail list logo