mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: MasterPrenium <masterprenium.lkml@gmail.com>
Cc: linux-kernel@vger.kernel.org, xen-users@lists.xen.org,
	linux-raid@vger.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: Wed, 4 Jan 2017 14:30:15 -0800	[thread overview]
Message-ID: <20170104223015.cr6vtyhxuwxrg76g@kernel.org> (raw)
In-Reply-To: <585D6C34.2020908@gmail.com>

On Fri, Dec 23, 2016 at 07:25:56PM +0100, MasterPrenium wrote:
> 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.

what did you mean 'huge' I/O (20M/s)? Is it possible you can reproduce the
issue with a raw raid5 raid? It would be even better if you can give me a fio
job file with the issue, so I can easily debug it.

also please check if upstream patch (e8d7c33 md/raid5: limit request size
according to implementation limits) helps.

Thanks,
Shaohua

  parent reply	other threads:[~2017-01-04 22:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 18:25 MasterPrenium
2016-12-26 13:14 ` MasterPrenium
2016-12-30 20:54 ` Jes Sorensen
2016-12-31  0:00   ` MasterPrenium
2017-01-04 22:30 ` Shaohua Li [this message]
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

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=20170104223015.cr6vtyhxuwxrg76g@kernel.org \
    --to=shli@kernel.org \
    --cc=MasterPrenium@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=masterprenium.lkml@gmail.com \
    --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

all inboxes | Powered by JetHome®