public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: mark@markschaefer.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: Booting from or using a Compaq RA4100 Array
Date: Thu, 29 Dec 2005 23:02:45 +0100	[thread overview]
Message-ID: <200512292302.50743@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <62187.24.3.12.198.1135893081.squirrel@www.markschaefer.org>

[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]

Mark Schaefer wrote:
>Eike,
>
>I think I've resigned myself to the fact that it won't boot.  I've done a
>bit of digging by directly sending commands to the unit.  I'm not sure why
>I can't force scsi_scan to do a REPORT_LUN on it through the Black List,
>but what I know is that it reports luns as 0x40...00 - 0x40...MAX_LUNS -
>they are reported as flat addressing, according to the SCSI Architecture
>Manual.
>
>Since TYPE_RAID implements a standard (albeit deprecated), it might
>actually be worth trying to create a driver for it.  The real question I
>have is whether I could get at the drives simply by masking the LUN's like
>the cpqfc driver does, or whether something like BLIST_SPARSE_LUNS would
>do the trick, or maybe even a new blasklist entry like
>BLIST_FLAT_LUN_ADDRESSING.
>
>Here's a quote from cpqfcTSworker.c:
>// e.g., the Compaq RA4x00 f/w Rev 2.54 and above may report
>// LUNs 4001, 4004, etc., because other LUNs are masked from
>// this HBA (owned by someone else).  We'll make those appear as
>// LUN 0, 1... to Linux

I've looked around a bit in the LUN code some month ago as I was trying to get 
this to a state where it was sort of working. This code is as horrible as the 
rest of this driver, so I didn't really got the point what of this strange 
stuff is really needed and what was just caused by code monkeys on drugs.

I now got a card, but a 5121, so I can't test this stuff. And I don't have 
such an array :)

>I'm not sure what the direction of Linux is at this point, but there are a
>lot of RA4x00's out there for cheap and they (at least initially) seemed
>like a good entry-level FC RAID system.

Now the driver is buried and all the people with such hardware come out of 
their holes. Fascinating :)) I was thinking about a list related only to 
these things and/or writing a FAQ for this. What do the other people around 
think about this? MKP?

>Also, I'm not sure how strange of 
>a beast the RA4x00 is.  If it's a one-off, maybe I could create a specific
>driver for it that acts as a LUN masker.  If there are more, it may make
>sense to make the changes necessary to deal with flat addressing.
>
>At this point, I'm convinced that it would be a minor change to at least
>the scsi_scan code to deal with TYPE_RAID.  I'm a bit more concerned about
>how widespread a change like flat addressing would be.

I'm not really familiar with the low level SCSI code. James? Christoph?

Eike

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-29 22:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 20:29 Booting from or using a Compaq RA4100 Array Mark Schaefer
2005-12-29  7:45 ` Rolf Eike Beer
2005-12-29 21:51   ` mark
2005-12-29 22:02     ` Rolf Eike Beer [this message]
2005-12-30 14:39       ` mark
2005-12-30 22:18       ` Martin K. Petersen
2006-01-02  2:22         ` Mark Schaefer
2006-01-02 16:18           ` Christoph Hellwig
2006-01-02 19:43           ` Martin K. Petersen
2006-01-03  7:51             ` Rolf Eike Beer
2006-01-03 12:34               ` Matthew Wilcox
2006-01-03 16:28                 ` Rolf Eike Beer
2006-01-03 19:20               ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 14:40 mark
2006-02-06 17:46 cpqfc gone - all compay RA4X00 Array now useless in linux? Ingo Flaschberger
2006-02-06 18:23 ` Rolf Eike Beer
2006-02-06 18:38   ` Ingo Flaschberger
2006-02-07  7:55     ` Rolf Eike Beer
2006-02-07 10:05       ` Booting from or using a Compaq RA4100 Array Ingo Flaschberger

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=200512292302.50743@bilbo.math.uni-mannheim.de \
    --to=eike-kernel@sf-tec.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark@markschaefer.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