From: Michal Feix <michal@feix.cz>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [SCSI] SCSI block devices larger then 2TB
Date: Wed, 07 Dec 2005 15:01:22 +0100 [thread overview]
Message-ID: <4396EB32.4010800@feix.cz> (raw)
In-Reply-To: <20051207123519.GA17414@infradead.org>
>>Greetings!
>>
>>Current aic79xxx driver doesn't see SCSI devices larger, then 2TB. It
>>fails with READ CAPACITY(16) command. As far as I can understand, we
>>already have LBD support in kernel for some time now. So it's only the
>>drivers, that need to be fixed? LSI driver is the only one I found
>>working with devices over 2TB; I couldn't test any other driver, as I
>>don't have the hardware. Is it really so bad, that only LSI chipset and
>>maybe few others are capable of seeng such devices?
>
>
> I definitly works fine with Qlogic parallel scsi and fibrechannel and emulex
> fibre channel controllers aswell as lsi/engenio megaraid controllers.
>
> It looks like aci79xx is just broken in that repsect. Unfortunately the
> driver doesn't have a proper maintainer, we scsi developers put in fixes
> and cleanups but we don't have the full documentation to fix such complicated
> issue. If you have a support contract with Adaptec complain to them.
As we do not have any special support contract with Adaptec, it's
probably a dead end. I found some aic79xx driver on Adaptec website for
2.6 kernel. It detects full SCSI device capacity, but it hangs
ocassionaly when that drive is beeing accessed, so it's unusable for
every day use.
Anyway, thanks for the info. And to everyone else, beware of Adaptec
SCSI host adapters when using large SCSI arrays... :(
next prev parent reply other threads:[~2005-12-07 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:21 [SCSI] SCSI block devices larger then 2TB Michal Feix
2005-12-07 12:35 ` Christoph Hellwig
2005-12-07 14:01 ` Michal Feix [this message]
2005-12-12 19:02 ` David Lang
2005-12-13 8:43 ` Michal Feix
2005-12-15 15:39 ` Roger Heflin
2005-12-19 22:33 ` David Lang
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=4396EB32.4010800@feix.cz \
--to=michal@feix.cz \
--cc=hch@infradead.org \
--cc=linux-kernel@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