On 17 Feb 2014, at 6:39 pm, Ulrich Windl
wrote:
Andrew Beekhof schrieb am 17.02.2014 um 02:33 in
Nachricht
> <7619a7e9-f006-4098-90f9-5c5b8bc84...@beekhof.net>:
>
>> On 11 Feb 2014, at 10:38 pm, Ulrich Windl
>>
>> wrote:
>
> [...]
>>> I did a quick check: It seems only "ocf:ocf
>>> Andrew Beekhof schrieb am 17.02.2014 um 02:33 in
>>> Nachricht
<7619a7e9-f006-4098-90f9-5c5b8bc84...@beekhof.net>:
> On 11 Feb 2014, at 10:38 pm, Ulrich Windl
> wrote:
[...]
>> I did a quick check: It seems only "ocf:ocfs2:o2cb" does such (IMHO)
> nonsense
>> like removing a module on st
On 11 Feb 2014, at 10:38 pm, Ulrich Windl
wrote:
Lars Marowsky-Bree schrieb am 05.02.2014 um 15:11 in
> Nachricht
> <20140205141140.gu13...@suse.de>:
>> On 2014-02-05T15:06:47, Ulrich Windl
> wrote:
>>
>>> I guess the kernel update is more common than the "just the ocfs2-kmp
> update"
>
>>> Lars Marowsky-Bree schrieb am 05.02.2014 um 15:11 in
Nachricht
<20140205141140.gu13...@suse.de>:
> On 2014-02-05T15:06:47, Ulrich Windl
wrote:
>
>> I guess the kernel update is more common than the "just the ocfs2-kmp
update"
>
> Well, some customers do apply updates in the recommended way,
On 2014-02-05T15:06:47, Ulrich Windl wrote:
> I guess the kernel update is more common than the "just the ocfs2-kmp update"
Well, some customers do apply updates in the recommended way, and thus
don't encounter this ;-) In any case, since at this time the cluster
services are already stopped, at
>>> Lars Marowsky-Bree schrieb am 05.02.2014 um 12:36 in
Nachricht
<20140205113649.gn13...@suse.de>:
> On 2014-02-05T12:24:00, Ulrich Windl
wrote:
>
>> I had a problem where "O2CB stop" fenced the node that was shut down:
>> I had updated the kernel, and then rebooted. As part of shutdown, the
