Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Dave Jones <davej@suse.de>,
	Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Additional BLIST_LARGELUN devices
Date: Thu, 27 Jun 2002 22:09:11 +0800	[thread overview]
Message-ID: <3D1B1C87.4020504@metaparadigm.com> (raw)
In-Reply-To: 20020626164744.GH3023@gum01m.etpnet.phys.tue.nl



On 06/27/02 00:47, Kurt Garloff wrote:

>Hi Marcello, Dave,
>
>here are some additional devices that need the BLIST_LARGELUN flag.
>

[snip]

>-	{"CNSI", "G7324", "*", BLIST_SPARSELUN},     // Chaparral G7324 RAID
>-	{"CNSi", "G8324", "*", BLIST_SPARSELUN},     // Chaparral G8324 RAID
>+	{"CMD", "CRA-7280", "*", BLIST_SPARSELUN | BLIST_LARGELUN},   // CMD RAID Controller
>+	{"CNSI", "G7324", "*", BLIST_SPARSELUN | BLIST_LARGELUN},     // Chaparral G7324 RAID
>+	{"CNSi", "G8324", "*", BLIST_SPARSELUN | BLIST_LARGELUN},     // Chaparral G8324 RAID
>

The G8324 correctly identifies itself as SCSI-3 so doesn't
need the BLIST_LARGELUN flag (proc output below
from 2.4.18 with automated large lun scanning).

This is as long as my fix for scanning large luns automatically
on SCSI-3 devices that went into 2.4.17-pre5 hasn't been
reverted in 2.4.19-pre

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: SEAGATE  Model: ST318405LC       Rev: 0105
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 06 Lun: 00
  Vendor: ESG-SHV  Model: SCA HSBP M10     Rev: 0.06
  Type:   Processor                        ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 50
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Processor                        ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 51
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Processor                        ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 52
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Processor                        ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 53
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Processor                        ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 00 Lun: 63
  Vendor: CNSi     Model: G8324            Rev: L411
  Type:   Processor                        ANSI SCSI revision: 03



  parent reply	other threads:[~2002-06-27 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 16:47 [PATCH] Additional BLIST_LARGELUN devices Kurt Garloff
2002-06-26 22:07 ` Kurt Garloff
2002-06-27 12:44   ` Michael Heinz
2002-06-27 14:09 ` Michael Clark [this message]
2002-06-27 14:53   ` Kurt Garloff
2002-06-27 20:22     ` Marcelo Tosatti
2002-06-27 21:28       ` Kurt Garloff

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=3D1B1C87.4020504@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=davej@suse.de \
    --cc=garloff@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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