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
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 cluster
> stack was stopped. In turn, the "O2CB" resource was stopped.
> Unfortunately this caused an error
Hi!
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 cluster
stack was stopped. In turn, the "O2CB" resource was stopped.
Unfortunately this caused an error like (SLES11 SP3):
---
modprobe: FATAL: Could no
