From: Jeremy Fitzhardinge <jeremy@goop.org>
To: chris <tknchris@gmail.com>
Cc: linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>,
Xen-Devel List <xen-devel@lists.xensource.com>
Subject: Re: Re: Weird Issue with raid 5+0
Date: Mon, 08 Mar 2010 15:26:42 -0800 [thread overview]
Message-ID: <4B9587B2.5050700@goop.org> (raw)
In-Reply-To: <31e44a111003080735t4ddf7c63uaa517ad6522cca67@mail.gmail.com>
On 03/08/2010 07:35 AM, chris wrote:
> I forwarding this to xen-devel because it appears to be a bug in dom0 kernel.
>
> I recently experienced a strange issue with software raid1+0 under Xen
> on a new machine. I was getting corruption in my guest volumes and
> tons of kernel messages such as:
>
> [305044.571962] raid0_make_request bug: can't convert block across
> chunks or bigger than 64k 14147455 4
>
> The full thread is located at http://marc.info/?t=126672694700001&r=1&w=2
> Detailed output at http://pastebin.com/f6a52db74
>
> It appears after speaking with the linux-raid mailing list that this
> is due a bug which has been fixed but the fix is not included in the
> dom0 kernel. I'm not sure what sources kernel 2.6.26-2-xen-amd64 is
> based on, but since xenlinux is still at 2.6.18 I was assuming that
> this bug would still exist.
>
There are a number of possible dom0 kernel in use. The xen.org
2.6.18-xen tree is still maintained on a bugfix basis. Are you seeing
the problem with 2.6.18-xen?
I don't know what 2.6.26-2-xen-amd64 is, but I'm guessing from the name
it is a Debian kernel. I don't know what its provenance is, but it is
not a xen.org supported kernel; if a fix is needed you should file a bug
against your distro.
Modern Xen kernels are based on 2.6.31.x and 2.6.32.x. See
http://wiki.xensource.com/xenwiki/XenParavirtOps and
http://wiki.xensource.com/xenwiki/XenDom0Kernels for more details.
J
next prev parent reply other threads:[~2010-03-08 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 4:33 Weird Issue with raid 5+0 chris
2010-02-21 5:48 ` Neil Brown
2010-02-21 7:26 ` chris
2010-02-21 8:16 ` Neil Brown
2010-02-21 8:21 ` Neil Brown
2010-02-21 9:17 ` chris
2010-02-21 10:35 ` chris
2010-03-08 5:50 ` Neil Brown
2010-03-08 6:16 ` chris
2010-03-08 7:05 ` Neil Brown
2010-03-08 15:35 ` chris
2010-03-08 17:29 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-03-09 19:42 ` Neil Brown
2010-03-08 23:26 ` Jeremy Fitzhardinge [this message]
2010-03-09 0:48 ` chris
2010-03-09 1:14 ` Jeremy Fitzhardinge
2010-03-08 20:14 ` Bill Davidsen
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=4B9587B2.5050700@goop.org \
--to=jeremy@goop.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tknchris@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.