All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terrence Martin <tmartin@physics.ucsd.edu>
To: Guy <bugzilla@watkins-home.com>
Cc: 'James Bottomley' <James.Bottomley@SteelEye.com>,
	'SCSI Mailing List' <linux-scsi@vger.kernel.org>
Subject: Re: Stock 2.6.4 with CONFIG_LBD=y and qla2xxx driver, reportswrongdevice size
Date: Wed, 24 Mar 2004 14:28:28 -0800	[thread overview]
Message-ID: <40620B8C.1080207@physics.ucsd.edu> (raw)
In-Reply-To: <200403242207.i2OM7wW19491@dns1.watkins-home.com>

Thanks Guy, I think I might just do that, create an MD device out of 3 
equal sized disks.

Where I may have gone wrong and gotten confused is that the Logical 
Drive limit is 64TB. However I have now read, and I assume it is still 
current, that each LUN is only 32bits limiting a LUN to 2TB. You then 
need some sort of additional RAID (hardware or software) presumably to 
map those LUNS to a single disk.

Linux RAID0 should handle this nicely I think.

Thanks

Terrence


Guy wrote:

>Beyond my knowledge...  Wish I was you!  :)
>
>But, if the device has a bug like "bit 33 lopped off".
>If he splits the array into 2 luns/devices then it may be fine.
>Then create the RAID0 with them.
>
>Guy
>
>-----Original Message-----
>From: James Bottomley [mailto:James.Bottomley@SteelEye.com] 
>Sent: Wednesday, March 24, 2004 5:01 PM
>To: Guy
>Cc: 'Terrence Martin'; 'SCSI Mailing List'
>Subject: RE: Stock 2.6.4 with CONFIG_LBD=y and qla2xxx driver,
>reportswrongdevice size
>
>On Wed, 2004-03-24 at 16:53, Guy wrote:
>  
>
>>This is just a guess!!!!!  But I think I am correct.
>>    
>>
>
>The standards are very explicit about what READ CAPACITY(10) should
>return for a >2TB device.  sd detects this and retries with a READ
>CAPACITY(16).
>
>There is no message in the log indicating this happened, so I think the
>device reported an incorrect size to READ CAPACITY(10).  It may have
>reported its size with bit 33 lopped off, but that's still a device
>problem.
>
>James
>
>
>
>  
>


      reply	other threads:[~2004-03-24 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 20:53 Stock 2.6.4 with CONFIG_LBD=y and qla2xxx driver, reports wrong device size Terrence Martin
2004-03-24 21:25 ` James Bottomley
2004-03-24 21:53   ` Stock 2.6.4 with CONFIG_LBD=y and qla2xxx driver, reports wrongdevice size Guy
2004-03-24 22:01     ` James Bottomley
2004-03-24 22:07       ` Stock 2.6.4 with CONFIG_LBD=y and qla2xxx driver, reportswrongdevice size Guy
2004-03-24 22:28         ` Terrence Martin [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=40620B8C.1080207@physics.ucsd.edu \
    --to=tmartin@physics.ucsd.edu \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bugzilla@watkins-home.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.