public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinay Venkataraghavan <raghavanvinay@yahoo.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: Number of devices that SCSI can support
Date: Wed, 9 Jan 2008 14:31:12 -0800 (PST)	[thread overview]
Message-ID: <145723.94801.qm@web43138.mail.sp1.yahoo.com> (raw)

Thank you all for responding. While I agree that the scsi stack in linux should be capable of supporting many targets, I still see this problem all the time. 
It seemed to consistently happen on /dev/sdbm which corresponds to the 65th lun or target.

My SAN configuration consists of: 4 targets with 16 luns each = 4 * 16 = 64 total devices.

But I ran another test by changing my targets information and saw this issue for /dev/sdbm 

As mentioned on this thread, I am attaching some more information. Looks like SCSI inquiry is going through, and the inquiry succeeds. As you can see from the attached message below the /sys/class/scsi_device file also gets created:
at /sys/class/scsi_device/1\:0\:3\:15/device/

and below this we find all the related entries such as:

block/          dump            queue_depth     state
delete          generic/        rescan          timeout
detach_state    model           rev             type
device_blocked  power/          scsi_level      vendor

So from this information it looks like the scsi mid layer had detected that particular lun. But the /dev/sdbm device has not been created. It was also mentioned that it could be a udev problem. 

The other curious issue is that if take the major number and the minor number from this entry and manually create the device file as such:

mknod /dev/sdbm 68 0 

it works after I rescan all the targets and luns and I am able to perform I/O on this lun. 

Any other ideas. 

Thanks,
Vinay

----- Original Message ----
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Vinay Venkataraghavan <raghavanvinay@yahoo.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>; linux-scsi@vger.kernel.org; Matthew Wilcox <matthew@wil.cx>
Sent: Wednesday, January 9, 2008 7:49:33 AM
Subject: Re: Number of devices that SCSI can support


On Wed, 09 Jan 2008, Matthew Wilcox wrote:

> On Wed, Jan 09, 2008 at 09:05:52AM -0600, James Bottomley wrote:
> > On Tue, 2008-01-08 at 19:22 -0700, Matthew Wilcox wrote:
> > > On Tue, Jan 08, 2008 at 04:55:46PM -0800, Vinay Venkataraghavan
 wrote:
> > > > Is there a limit on the number of devices that SCSI supports.
 In other words, I have a QLogic HBA card, and I am connecting to a SAN
 which has 64 targets. 
> > > 
> > > I've personally had over five hundred LUNs.  You shouldn't be
 hitting a
> > > limit here.
> > 
> > I believe the largest test that's been run was the old OSDL CGL
> > workgroup ... they went up to 4096.
> > 
> > However, LUN support depends on the driver and HBA parameters as
 well
> > (some choose to have arbitrary limits).
> 
> I was using a qlogic HBA for my tests, so I don't think this is the
> problem -- although the original poster claims to have 64 targets,
 and I
> had only one target with 128 luns (attached 4 times).
> 
> -- 
> Intel are signing my paycheques ... these opinions are still mine
> "Bill, look, we understand that you're interested in selling us this
> operating system, but compare it to ours.  We can't possibly take
 such
> a retrograde step."

Not sure what's going on as well, perhaps some logs could help... But
the inbox qla2xxx driver in RHEL4 set's an HBA's scsi_host->max_id
count to 512 (also verified with several test rings), so there
shouldn't be a problem handling 64 distinct targets (FC ports).
-
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





      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs


             reply	other threads:[~2008-01-09 22:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 22:31 Vinay Venkataraghavan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-10 14:18 Number of devices that SCSI can support Ellison, Bob
2008-01-10 15:15 ` berthiaume_wayne
2008-01-09  0:55 Vinay Venkataraghavan
2008-01-09  2:22 ` Matthew Wilcox
2008-01-09 12:42   ` Jansen, Frank
2008-01-09 15:05   ` James Bottomley
2008-01-09 15:36     ` Matthew Wilcox
2008-01-09 15:49       ` Andrew Vasquez

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=145723.94801.qm@web43138.mail.sp1.yahoo.com \
    --to=raghavanvinay@yahoo.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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