smartmontools with aac

[Don Bowman]

From: Scott Long [mailto:scottl at freebsd.org]
> Don Bowman wrote:
> > is there a way to use smartmontools with
> > aac?
> > 
> > e.g. smartctl wants to see 'ad0' or 'da0'
> > as the disk to connect to. For aac, it is
> > aacd0. Specifying:
> > 
> > smartctl -i -d scsi -a aacd0
> > gives
> > Smartctl open device: aacd0 failed: Inappropriate ioctl for device
> > 
> > I'm not really sure what ioctl are being used,
> > i guess i should look in the smartmontool source.
> > 
> > --don
> 
> AAC containers do not export SMART events.  You can monitor individual
> disks by enabling the aacp driver and watching the /dev/passN devices,
> or you can script the aaccli to report events for you.

So i was tracking down why i can't do a 'camcontrol inq'
on aac.

When i do:

camcontrol inq 0:2 -v
I get:
pass1: <IBM IC35L146UCDY10-0 S27E> Fixed unknown SCSI-3 device 
CAM status is 0x12
[long pause, ~30s?]
camcontrol: error getting transfer settings
CAM status is 0x6

camcontrol cmd pass1 -v -c "12 01 00 00 01 00" -i 1 "b3 b5"
0 31 
----------

According to the docs, the second of these numbers should be 0, unless
the LUN (pass1) is not present, in which case 31 is correct, but then
the first number should be 3.  Maybe this is what the RAID is botching, 
and what "camcontrol inquiry" can't handle to get the serial number.

Byte |                       Bit
     | 7       6       5      | 4   3   2   1   0
 0   | Peripheral Device Type | Peripheral Qualifier

"Peripheral Qualifier is set to zero to indicate that the LUN 
specified in the IDENTIFY Message is currently supported. Peripheral 
Qualifier is set to 011b when the LUN specified in the IDENTIFY
Message is not present.

Peripheral Device Type is set to zero to indicate that the device is 
a Direct-Access. Peripheral Device Type is set to 1Fh when the LUN 
specified in the IDENTIFY Message is not present."