Re: Accessing SCSI-Devices >2TB

From: Scott Long <scottl_at_samsco.org>
Date: Mon, 13 Jun 2005 22:36:39 -0600
Kenneth D. Merry wrote:

> On Mon, Jun 13, 2005 at 12:19:15 +0200, Raphael H. Becker wrote:
> 
>>PS+BTW: any idea why the internal PERC is not listed in camcontrol devlist?
>>
>>In dmesg its listed like
>>aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4
>>aac0: i960RX 100MHz, 118MB cache memory, optional battery present
>>aac0: Kernel 2.7-1, Build 3170, S/N 5410d3
>>aac0: Supported Options=75c<WCACHE,DATA64,HOSTTIME,WINDOW4GB,SOFTERR,NORECOND,SGMAP64>
>>[...]
>>aacd0: <RAID 5> on aac0
>>aacd0: 69425MB (142182912 sectors)
>>
>>pciconf:
>>aac0_at_pci4:8:1:  class=0x010400 card=0x01211028 chip=0x000a1028 rev=0x01 hdr=0x00
>>    vendor   = 'Dell Computer Corporation'
>>    device   = 'PowerEdge 3/Di Expandable RAID Controller'
>>    class    = mass storage
>>    subclass = RAID
>>
>>It's not SCSI?
> 
> 
> It is a SCSI RAID controller, but the interface to the OS is a block
> interface, not a SCSI interface (*).  It isn't routed through the SCSI
> layer, since that wouldn't really help it that much.
> 
> (*) There is a SCSI passthrough interface for some aac controllers that
> can be enabled via the aacp driver.
> 
> Ken

And the aacp device causes many more problems than it solves, so I'll 
likely be disabling it soon.  It only provides simple userland SCSI 
access to cdroms and tape drives, anyways.

Scott
Received on Tue Jun 14 2005 - 02:39:13 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:36 UTC