On Mon, 2018-03-05 at 10:44 +0100, Jean-Louis Dupond wrote:
> Maby a long shot, but could it be fixed by
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/block/loop.c?h=v4.9.86&id=56bc086358cac1a2949783646eabd57447b9d672
>
> ?
> Or shouldn't that fix such
Hi,
Maby a long shot, but could it be fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/block/loop.c?h=v4.9.86&id=56bc086358cac1a2949783646eabd57447b9d672
?
Or shouldn't that fix such kind of issues?
It seems like some kind of race condition, caus
On Sun, 2018-03-04 at 20:01 +0100, Jean-Louis Dupond wrote:
> I'm running indeed CentOS 6 with the Virt SIG kernels. Already updated
> to 4.9.75, but recently hit the problem again.
>
> The first PID that was in D-state (root 27157 0.0 0.0 127664 5196
> ?D06:19 0:00 \_ vgdi
Hi Bart,
Thanks for your answer.
I'm running indeed CentOS 6 with the Virt SIG kernels. Already updated
to 4.9.75, but recently hit the problem again.
The first PID that was in D-state (root 27157 0.0 0.0 127664 5196
?D06:19 0:00 \_ vgdisplay -c --ignorelockingfailure),
On 02/05/18 08:01, Jean-Louis Dupond wrote:
We've got some "strange" issue on a Xen hypervisor with CentOS 6 and
4.9.63-29.el6.x86_6 kernel.
Hello Jean-Louis,
Since this behavior was observed with a distro kernel I think a support
request should be submitted to the vendor of that kernel. That
Hi,
Nobody any idea's on this?
Would be nice to have some pointers at least :)
Thanks
Jean-Louis
Op 2018-02-05 17:01, schreef Jean-Louis Dupond:
Hi All,
We've got some "strange" issue on a Xen hypervisor with CentOS 6 and
4.9.63-29.el6.x86_6 kernel.
The system has a local raid + is connected