From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: failover does not work with rdac device handler
Date: Fri, 26 Jun 2009 10:42:51 -0700 [thread overview]
Message-ID: <1246038171.14164.19.camel@chandra-ubuntu> (raw)
In-Reply-To: <4A4493CB.6040009@meteo.uni-koeln.de>
On Fri, 2009-06-26 at 11:24 +0200, Mario Mech wrote:
> Chandra Seetharaman schrieb:
> > On Wed, 2009-06-24 at 18:09 +0200, Mario Mech wrote:
> >> Hi,
> >>
> >> I need help with a similar or even the same issue as in the thread mentioned in the Subject
> >> (https://www.redhat.com/archives/dm-devel/2008-October/msg00130.html).
> >
> > My bad. I had some issues during debug and never got back to it.
> >
> > Will send couple of patches by tomorrow to fix this problem.
> >
>
> That sounds great.
>
> >> At the moment I'd like to avoid building the multipath package by myself with the patch provided in the afore mentioned thread.
> >
> > The changes are in kernel code.
> >> Do you have any ideas? Or is a different problem I have.
> >
> > It is the same problem and I am afraid that you do not have a way out.
> >
> > May be next version of RHEL might add your device to rdac_dev_list (if
> > you could do that that would fix the problem).
> >
>
> I assume it's only building new kernel modules for my running 2.6.18-128.1.14.el5. That shouldn't be a big deal.
Yes. MD3000i is already in mainline code, you can just cut-n-paste that
entry for rdac_dev_list, compile the module and you are good to do.
chandra
>
> >> Every help is appreciated.
> >>
> >> All best
> >>
> >> Mario
> >>
> >
> > --
> > dm-devel mailing list
> > dm-devel@redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
>
>
next prev parent reply other threads:[~2009-06-26 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 16:09 failover does not work with rdac device handler Mario Mech
2009-06-24 20:29 ` Charlie Brady
2009-06-26 17:41 ` Chandra Seetharaman
2009-06-26 0:56 ` Chandra Seetharaman
2009-06-26 9:24 ` Mario Mech
2009-06-26 17:42 ` Chandra Seetharaman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 17:01 Patch: add Dell product information into " Yanqing_Liu
2008-10-01 21:47 ` failover does not work with " Moger, Babu
2008-10-04 0:12 ` Moger, Babu
2008-10-04 0:50 ` [dm-devel] " Chandra Seetharaman
2008-10-04 3:35 ` Moger, Babu
2008-10-06 19:26 ` Moger, Babu
2008-10-06 19:53 ` [dm-devel] " Chandra Seetharaman
2008-10-06 19:59 ` Moger, Babu
2008-10-06 22:26 ` Moger, Babu
2008-10-07 2:04 ` [dm-devel] " Chandra Seetharaman
2008-10-07 18:34 ` Moger, Babu
2008-10-07 19:19 ` [dm-devel] " Chandra Seetharaman
2008-10-07 20:26 ` Moger, Babu
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=1246038171.14164.19.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=sekharan@linux.vnet.ibm.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