From: MasterPrenium <masterprenium.lkml@gmail.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-kernel@vger.kernel.org, xen-users@lists.xen.org,
linux-raid@vger.kernel.org, shli@kernel.org,
"MasterPrenium@gmail.com" <MasterPrenium@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: PROBLEM: Kernel BUG with raid5 soft + Xen + DRBD - invalid opcode
Date: Sat, 31 Dec 2016 01:00:31 +0100 [thread overview]
Message-ID: <5866F51F.3050702@gmail.com> (raw)
In-Reply-To: <wrfj8tqxf89j.fsf@redhat.com>
Hello,
Thanks for your reply. DRBD isn't part of the kernel ? I was thinking it
has been included since 2.6.3x ?
I've just tested without DRBD, the issue seems to remain. Can't see the
"BUG", but the kernel crashed also. (A little bit later)
I don't have full dump since I lost my network connection and my serial
connection.
Here is a picture of what I got :
http://img15.hostingpics.net/pics/113882KernelError6.png
Another one : http://img11.hostingpics.net/pics/164702KernelError7.png
It also seems to me that having the "glances" monitoring software
running in dom0, makes the kernel crashes quicker, don't think this can
help but... just in case...
Any idea / test I can make ? This is really a blocking issue with
potential data loss...
Best regards,
MasterPrenium
Le 30/12/2016 21:54, Jes Sorensen a écrit :
> MasterPrenium<masterprenium.lkml@gmail.com> writes:
>> Hello Guys,
>>
>> I've having some trouble on a new system I'm setting up. I'm getting a
>> kernel BUG message, seems to be related with the use of Xen (when I
>> boot the system _without_ Xen, I don't get any crash).
>> Here is configuration :
>> - 3x Hard Drives running on RAID 5 Software raid created by mdadm
>> - On top of it, DRBD for replication over another node (Active/passive cluster)
>> - On top of it, a BTRFS FileSystem with a few subvolumes
>> - On top of it, XEN VMs running.
>>
>> The BUG is happening when I'm making "huge" I/O (20MB/s with a rsync
>> for example) on the RAID5 stack.
>> I've to reset system to make it work again.
>>
>> Reproducible : ALWAYS (making the i/o, it crash in 2-5mins). Also
>> reproducible on another system with the same hardware.
>>
>> Kernel versions impacted (at least): kernel-4.4.26, kernel-4.8.15, kernel-4.9.0
> Well you have one foreign object in there that is not part of the
> kernel and which shows up in the OOPS: DRDB
>
> What happens when you remove that from the equation?
>
> Jes
next prev parent reply other threads:[~2016-12-31 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 18:25 PROBLEM: Kernel BUG with raid5 soft + Xen + DRBD - invalid opcode MasterPrenium
2016-12-26 13:14 ` MasterPrenium
2016-12-30 20:54 ` Jes Sorensen
2016-12-31 0:00 ` MasterPrenium [this message]
2017-01-04 22:30 ` Shaohua Li
2017-01-05 14:16 ` MasterPrenium
2017-01-05 19:37 ` Shaohua Li
2017-01-08 13:31 ` MasterPrenium
2017-01-09 22:44 ` Shaohua Li
2017-01-17 1:54 ` MasterPrenium
2017-05-13 0:06 ` MasterPrenium
2017-05-13 10:55 ` MasterPrenium
2017-05-15 0:59 ` Fwd: " MasterPrenium
2017-10-05 21:35 ` MasterPrenium
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5866F51F.3050702@gmail.com \
--to=masterprenium.lkml@gmail.com \
--cc=Jes.Sorensen@redhat.com \
--cc=MasterPrenium@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xen-users@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).