From: Kevin Corry <kevcorry@us.ibm.com>
To: evms-devel@lists.sourceforge.net
Cc: Lars Marowsky-Bree <lmb@suse.de>,
syrius.ml@no-log.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.10-ac10 + 2.6.10udm1 + latest evms => not nice
Date: Fri, 21 Jan 2005 12:04:56 -0600 [thread overview]
Message-ID: <200501211204.56232.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20050121144738.GM25714@marowsky-bree.de>
On Friday 21 January 2005 8:47 am, Lars Marowsky-Bree wrote:
> On 2005-01-21T15:13:26, syrius.ml@no-log.org wrote:
> > Don't know if it's related to evms or to dm.
> > kernel is a 2.6.10-ac10 + 2.6.10-udm1 + evms kernel patches.
> > (bd_claims + dm bbr + dm multipath)
> >
> > Here is the nice welcome message I've just got :)
>
> This looks like md on DM breakage, which Jens has just fixed in our
> kernel. I'm not sure whether he has submitted it upstream yet, but you
> can give it a try.
>
> Does the attached patch apply & fix the problem for you?
> If md resides on top of a driver using bio_clone() (such as dm), it will
> oops the kernel due to md submitting a botched bio that has a veclist but
> doesn't have bio->bi_max_vecs set.
Is there a specific scenario that causes the kernel to oops if an MD device is
made of DM devices? EVMS has been using this kind of configuration for a
couple years, and we've never noticed a problem with it. Also, syrius
mentioned on IRC that this problem only started occurring with -ac10, and
that -ac8 worked fine. I'm checking out the diffs between those two versions
to see what else might have changed.
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Evms-devel mailing list
Evms-devel@lists.sourceforge.net
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel
next prev parent reply other threads:[~2005-01-21 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87brbinaey.87acr2naey@878y6mnaey.message.id>
2005-01-21 14:47 ` [Evms-devel] 2.6.10-ac10 + 2.6.10udm1 + latest evms => not nice Lars Marowsky-Bree
2005-01-21 17:53 ` syrius.ml
2005-01-21 18:04 ` Kevin Corry [this message]
[not found] ` <200501210901.11031.kevcorry@us.ibm.com>
2005-01-21 18:05 ` Kevin Corry
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=200501211204.56232.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.de \
--cc=syrius.ml@no-log.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).