public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ionut Nistor" <ionut@modulo.ro>
To: Ionut Nistor <ionut@wsp.ro>, andrew@fc.hp.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: Support for lun > 7 on HP's XP128 storage
Date: Fri, 20 Jun 2003 14:08:19 +0300	[thread overview]
Message-ID: <00e901c3371c$42117c40$0cc7e7c1@EEL> (raw)
In-Reply-To: 1562.193.231.199.62.1055959426.squirrel@mail.wsp.ro

Sorry for being coming back on the same issue but should this (blacklisting
for XP) not be included in the kernel?

Thanks,
Ionut

----- Original Message ----- 
From: "Ionut Nistor" <ionut@wsp.ro>
To: <andrew@fc.hp.com>
Cc: <ionut@modulo.ro>
Sent: Wednesday, June 18, 2003 9:03 PM
Subject: Re: Support for lun > 7 on HP's XP128 storage


> Hello Andrew,
>
> I know this, but I was hoping this gets included in the kernel's blacklist
> - should be since this is how XP works.
>
> By the way, do you happen to know why XP reports SCSI ver 2 but allows
> more than 8 LUNs? This sort of breaks the standard.
>
> Thanks,
> Ionut
>
> > On Wed, 2003-06-18 at 00:16, Ionut Nistor wrote:
> >> Hello,
> >>
> >> I am running a 2.4.18-ac3 kernel on a ia32 system.
> >> This system is connected to a SAN via an Emulex LP8000 HBA. The
> >> storage is HP's XP128. The controller on the storage reports scsi
> >> version 2 however, luns with ID > 7 are also supported. When the HBA
> >> driver is loaded, no LUNs are detected but if "scsi add-single-device"
> >> is used later, the luns are visible.
> >>
> >> Maybe it should be added to the kernel with BLIST_LARGELUN - correct
> >> me if I am wrong.
> >>
> >> Thanks,
> >> Ionut
> >>
> >
> > Try adding the following entries to the device_list in scsi_scan.c:
> >
> > {"HP", "OPEN-", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
> > {"HP", "DISK-SUBSYSTEM", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
> >
> >
> >
> >> -
> >> To unsubscribe from this list: send the line "unsubscribe linux-scsi"
> >> in the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>
> > --
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >    Andrew Patterson                          Voice:  (970) 898-3261
> > Hewlett-Packard Company                   Email:  andrew@fc.hp.com
>
>
>
>


      parent reply	other threads:[~2003-06-20 10:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18  6:16 Support for lun > 7 on HP's XP128 storage Ionut Nistor
     [not found] ` <1055942750.8263.10.camel@lvadplx>
     [not found]   ` <1562.193.231.199.62.1055959426.squirrel@mail.wsp.ro>
2003-06-20 11:08     ` Ionut Nistor [this message]

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='00e901c3371c$42117c40$0cc7e7c1@EEL' \
    --to=ionut@modulo.ro \
    --cc=andrew@fc.hp.com \
    --cc=ionut@wsp.ro \
    --cc=linux-scsi@vger.kernel.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