From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Sun StorageTek 2530 and dm?
Date: Mon, 24 Aug 2009 14:06:01 -0700 [thread overview]
Message-ID: <1251147961.24406.34.camel@chandra-ubuntu> (raw)
In-Reply-To: <20090824225324.1ee86d9f@pc-jsosic.srce.hr>
On Mon, 2009-08-24 at 22:53 +0200, Jakov Sosic wrote:
> On Mon, 24 Aug 2009 13:44:34 -0700
> Chandra Seetharaman <sekharan@us.ibm.com> wrote:
>
> > ok.. simple words; That patch won't help you.
>
> hm :( so defining "SUN" "LCMS100_S" won't help? Although in
> scsi_dh_rdac only "SUN" "LCMS100_F" is defined. And that stands for
> Fiber, while mine is SAS cabling...
Adding this to scsi_dh_rdac makes sure that the module recognizes your
device at boot time itself (provided you have it in your initrd image).
>
> I've recompiled RPM with added patch, then extracted single module
> (scsi_dh_rdac.ko), and put it in place of the original module...
>
> FATAL: Error inserting scsi_dh_rdac
> (/lib/modules/2.6.18-128.4.1.el5xen/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko):
> Invalid module format
Hmm, just that change should cause this. BTW, can you provide the patch
you are trying to add.
Can you also provide the (current) o/p of "multipath -ll" and
current /etc/multipath.conf.
>
> I guess I'll have to build the whole kernel just because of this :(
>
>
>
> > This is uncalled for!!
>
> Sorry, I'm easily flammable...
but doesn't help the cause :).. lets stay objective here :)
>
>
>
>
next prev parent reply other threads:[~2009-08-24 21:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 19:05 Sun StorageTek 2530 and dm? Jakov Sosic
2009-08-23 19:34 ` Jakov Sosic
2009-08-24 15:41 ` Charlie Brady
2009-08-24 15:48 ` Jakov Sosic
2009-08-24 16:00 ` Jakov Sosic
2009-08-24 18:38 ` Chandra Seetharaman
2009-08-24 18:55 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman
2009-08-24 20:37 ` Jakov Sosic
2009-08-24 20:44 ` Chandra Seetharaman
2009-08-24 20:53 ` Jakov Sosic
2009-08-24 21:06 ` Chandra Seetharaman [this message]
2009-08-24 21:37 ` Jakov Sosic
2009-08-24 21:54 ` Chandra Seetharaman
2009-08-24 22:58 ` Charlie Brady
2009-08-24 23:09 ` Jakov Sosic
2009-08-24 23:18 ` Chandra Seetharaman
2009-08-24 23:22 ` Jakov Sosic
2009-08-24 23:11 ` Chandra Seetharaman
2009-08-24 23:11 ` Jakov Sosic
2009-08-24 18:29 ` Jakov Sosic
2009-08-24 18:48 ` Chandra Seetharaman
2009-08-24 18:59 ` Jakov Sosic
2009-08-24 20:24 ` Chandra Seetharaman
2009-08-24 20:36 ` Jakov Sosic
2009-08-24 20:57 ` Chandra Seetharaman
2009-08-24 21:14 ` Jakov Sosic
2009-08-24 21:41 ` Chandra Seetharaman
2009-08-24 21:53 ` Jakov Sosic
2009-08-24 23:07 ` Chandra Seetharaman
2009-08-24 23:13 ` Jakov Sosic
2009-08-25 0:06 ` Jakov Sosic
2009-08-25 0:18 ` Chandra Seetharaman
2009-08-25 3:36 ` Charlie Brady
2009-08-25 18:07 ` Chandra Seetharaman
2009-08-25 19:21 ` Charlie Brady
2009-08-25 19:55 ` Chandra Seetharaman
2009-08-25 20:51 ` Charlie Brady
2009-08-25 21:09 ` Jakov Sosic
2009-08-26 21:57 ` Charlie Brady
2009-08-26 22:31 ` Chandra Seetharaman
2009-08-26 23:01 ` Charlie Brady
2009-08-27 8:30 ` Jakov Sosic
2009-08-27 16:02 ` Charlie Brady
2009-08-27 19:11 ` Chandra Seetharaman
2009-08-24 21:19 ` Jakov Sosic
2009-08-24 21:43 ` Chandra Seetharaman
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=1251147961.24406.34.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 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.