From: Neil Brown <neilb@suse.de>
To: Neil Brown <neilb@suse.de>
Cc: chris <tknchris@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Weird Issue with raid 5+0
Date: Sun, 21 Feb 2010 19:21:07 +1100 [thread overview]
Message-ID: <20100221192107.2ede0267@notabene.brown> (raw)
In-Reply-To: <20100221191640.39b68b01@notabene.brown>
On Sun, 21 Feb 2010 19:16:40 +1100
Neil Brown <neilb@suse.de> wrote:
> On Sun, 21 Feb 2010 02:26:42 -0500
> chris <tknchris@gmail.com> wrote:
>
> > That is exactly what I didn't want to hear :( I am running
> > 2.6.26-2-xen-amd64. Are you sure its a kernel problem and nothing to
> > do with my chunk/block sizes? If this is a bug what versions are
> > affected, I'll build a new domU kernel and see if I can get it working
> > there.
> >
> > - chris
>
> I'm absolutely sure it is a kernel bug.
though it just occurs to me that you might be able to work around it.
If, in the guest, you set "max_sectors_kb" to "4"
in /sys/block/whatever/queue, it might avoid the problem.
NeilBrown
> I have no idea what version might be affected. Probably all, but
> as xen isn't fully in main line it isn't easy for me to explore.
>
> I suggest you contact the xen developers (or whoever you got xen from).
> I'm happy to discuss the problem with someone who knows about xen block
> device access, but I don't want to go hunting to find such a person.
>
> NeilBrown
next prev parent reply other threads:[~2010-02-21 8:21 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 [this message]
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
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=20100221192107.2ede0267@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=tknchris@gmail.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 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).