From: scameron@beardog.cca.cpqcorp.net
To: linux-kernel@vger.kernel.org
Cc: James.Bottomley@HansenPartnership.com, mike.miller@hp.com,
fujita.tomonori@lab.ntt.co.jp
Subject: Re: HP (Compaq) Smart Array 5xxx controller SCSI driver
Date: Wed, 23 Jul 2008 10:50:05 -0500 [thread overview]
Message-ID: <20080723155005.GF8833@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20080722175537.GB8833@beardog.cca.cpqcorp.net>
Fujita Tomonori wrote:
> I created symbolic links (neat udev rules can do automatically).
>
> clover:/home/fujita# ls -l /dev/cciss/
> total 0
> lrwxrwxrwx 1 root root 8 2008-07-23 21:38 c0d0 -> /dev/sde
> lrwxrwxrwx 1 root root 9 2008-07-23 21:39 c0d0p1 -> /dev/sde1
> lrwxrwxrwx 1 root root 9 2008-07-23 21:39 c0d0p2 -> /dev/sde2
> lrwxrwxrwx 1 root root 8 2008-07-23 21:38 c0d1 -> /dev/sdf
> lrwxrwxrwx 1 root root 8 2008-07-23 21:38 c0d2 -> /dev/sdg
> lrwxrwxrwx 1 root root 8 2008-07-23 21:38 c0d3 -> /dev/sdh
>
> The symbolic links enable users to mount the device as before.
>
> hpacucli seems to work (I didn't try all the commands but the point is
> that we can provide the ioctl compatibility):
That's pretty neat, I'm surprised that works. Obviously
you've got the needed ioctls already done.
I bet if you deleted all the logical drives it wouldn't work
anymore (because /dev/cciss/c0d0 -> /dev/sde would disappear.)
A way around that would be to present a device to the linux
kernel with 8-byte LUN address of all zeroes mapped to some
bus/target/lun. When the SCSI scan happens and the inquiry
is sent down to this address, the RAID controller will respond.
Then let sg bind to that, and get ACU to use the sg device.
(I hope it's clear what I'm saying.)
I don't know if the udev rules can be made smart enough to
point /dev/cciss/c0d0 at the sg device if there are no
logical drives, and at the first logical drive if there
is at least one. In the longer term, ACU would have to
be changed to use that sg device always rather than using
/dev/cciss/c0d0.
In the cciss driver, we always present /dev/cciss/c0d0
whether there are any logical drives or not for this reason,
a rather clunky solution.
-- steve
next parent reply other threads:[~2008-07-23 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080722175537.GB8833@beardog.cca.cpqcorp.net>
2008-07-23 15:50 ` scameron [this message]
2008-07-24 1:32 ` FUJITA Tomonori
2008-07-22 17:57 scameron
2008-07-24 1:32 ` FUJITA Tomonori
2008-07-24 13:30 ` scameron
2008-07-24 13:44 ` FUJITA Tomonori
2008-07-24 13:54 ` scameron
2008-07-24 15:00 ` Miller, Mike (OS Dev)
2008-07-24 15:06 ` FUJITA Tomonori
2008-08-07 19:04 ` Miller, Mike (OS Dev)
2008-08-08 1:07 ` FUJITA Tomonori
2008-08-08 15:32 ` Miller, Mike (OS Dev)
2008-07-24 17:47 ` Andrew Patterson
2008-07-24 16:02 ` scameron
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=20080723155005.GF8833@beardog.cca.cpqcorp.net \
--to=scameron@beardog.cca.cpqcorp.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.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
all inboxes | Powered by JetHome®