On 21/06/16 12:19 PM, Ken Gaillot wrote:
> On 06/17/2016 07:05 AM, Vladislav Bogdanov wrote:
>> 03.05.2016 01:14, Ken Gaillot wrote:
>>> On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
Hi,
Just found an issue with node is silently unfenced.
That is quite large setup (2
On 06/17/2016 07:05 AM, Vladislav Bogdanov wrote:
> 03.05.2016 01:14, Ken Gaillot wrote:
>> On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
>>> Hi,
>>>
>>> Just found an issue with node is silently unfenced.
>>>
>>> That is quite large setup (2 cluster nodes and 8 remote ones) with
>>> a plenty
17.06.2016 15:05, Vladislav Bogdanov wrote:
03.05.2016 01:14, Ken Gaillot wrote:
On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
Hi,
Just found an issue with node is silently unfenced.
That is quite large setup (2 cluster nodes and 8 remote ones) with
a plenty of slowly starting resources
03.05.2016 01:14, Ken Gaillot wrote:
On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
Hi,
Just found an issue with node is silently unfenced.
That is quite large setup (2 cluster nodes and 8 remote ones) with
a plenty of slowly starting resources (lustre filesystem).
Fencing was initiated
On 04/19/2016 10:47 AM, Vladislav Bogdanov wrote:
> Hi,
>
> Just found an issue with node is silently unfenced.
>
> That is quite large setup (2 cluster nodes and 8 remote ones) with
> a plenty of slowly starting resources (lustre filesystem).
>
> Fencing was initiated due to resource stop
Hi,
Just found an issue with node is silently unfenced.
That is quite large setup (2 cluster nodes and 8 remote ones) with
a plenty of slowly starting resources (lustre filesystem).
Fencing was initiated due to resource stop failure.
lustre often starts very slowly due to internal recovery, and
