afacli aborts on "open afa0"

Carlos Antunes cmantunes at nowthor.com
Sun Jul 22 18:53:27 CDT 2007


Hello!

I just installed afacli on a PowerEdge 2650 running Debian Etch and 
created the corresponding /dev/afa0. After afacli shows me the prompt, I 
enter "open afa0". At this point, the program exists with an "Aborted". 
Starting the program with options "-m ADAPTER -l 5 " allowed to capture 
the following:

 2665 -1210266784 DEBUG -> fcux_AddCommandToList, [SIZE:200], [LINE:open 
"afa0"]
 2665 -1210266784 DRIVE -> faos_OpenChannelToAdapter
 2665 -1210266784 DRIVE -> faux_mbAdapterNameFromWide
 2665 -1210266784 DRIVE -> faux_mbAdapterNameFromWide: (NAME=afa0)
 2665 -1210266784 DRIVE -> faux_IsAdapterNameValid: (NAME=afa0)
 2665 -1210266784 DRIVE -> FsaUxGetDeviceNamePrefix
 2665 -1210266784 DRIVE <- FsaUxGetDeviceNamePrefix: afa
 2665 -1210266784 DRIVE -> faux_IsAdapterNameValid: (NAME=afa0), 
(OEM=afa), (Match=YES)
 2665 -1210266784 DRIVE -- faos_OpenChannelToAdapter, opened file 
/dev/afa0, fd= 4
 2665 -1210266784 DRIVE -- faos_OpenChannelToAdapter: st_dev=13, 
st_ino=3206, st_mode= 0x00002180 --- l- rw-------, st_nlink=1, st_uid=0, 
st_gid=0,
 2665 -1210266784 DRIVE                               st_rdev=65024, 
st_size=0, st_blksize=4096, st_blocks=0,
 2665 -1210266784 DRIVE                               st_atim=Sun Jul 22 
19:33:3
3 2007, st_mtim=Sun Jul 22 19:33:33 2007, st_ctim=Sun Jul 22 19:35:28 2007
 2665 -1210266784 DRIVE -> faux_FillAdapterInfoStruct
 2665 -1210266784 FIB   -- faux_FillAdapterInfoStruct: Size=4, 
StructType=TFib,
Command=RequestAdapterInfo:
 2665 -1210266784 IOCTL -- faux_FillAdapterInfoStruct, Passed 
ioctl:FSACTL_SENDF
IB
 2665 -1210266784 DRIVE <- faux_FillAdapterInfoStruct
 2665 -1210266784 DRIVE -- faos_OpenChannelToAdapter, /dev/afa0 is 
really an ada
pter, [FD=4]
 2665 -1210266784 DRIVE <- faos_OpenChannelToAdapter /dev/afa0 with 
[FD=4] passe
d
 2665 -1210266784 DRIVE <- faos_OpenChannelToAdapter
 2665 -1210266784 FIB   -> faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=4, StructType=TFib, 
Command
=IsAdapterPaused:
 2665 -1210266784 IOCTL -- faos_SendReceiveFIB, Passed FSACTL_SENDFIB
 2665 -1210266784 FIB   <- faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -> faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=464, 
StructType=TFib, Comma
nd=ContainerCommand:GET_SCSI_METHOD
 2665 -1210266784 IOCTL -- faos_SendReceiveFIB, Passed FSACTL_SENDFIB
 2665 -1210266784 FIB   <- faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -> faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=12, 
StructType=TFib, Comman
d=CheckRevision:
 2665 -1210266784 IOCTL -- faos_SendReceiveFIB, Passed FSACTL_SENDFIB
 2665 -1210266784 FIB   <- faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -> faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=4, StructType=TFib, 
Command
=RequestAdapterInfo:
 2665 -1210266784 IOCTL -- faos_SendReceiveFIB, Passed FSACTL_SENDFIB
 2665 -1210266784 FIB   <- faos_SendReceiveFIB with fd=4
 2665 -1210266784 DRIVE -> faos_CheckDriverCompatibility
 2665 -1210266784 IOCTL -- faos_CheckDriverCompatibility, Passed 
ioctl:FSACTL_MI
NIPORT_REV_CHECK
 2665 -1210266784 DRIVE -- faos_CheckDriverCompatibility: 
miniportDriverVersion:
 BN=2409, dash=5, type=4, minor=1, major=1
 2665 -1210266784 DRIVE -- faos_CheckDriverCompatibility: 
fileSysDriverVersion:
BN=2409, dash=5, type=4, minor=1, major=1
 2665 -1210266784 DRIVE <- faos_CheckDriverCompatibility
 2665 -1210266784 FIB   -> faos_SendReceiveFIB with fd=4
 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=464, 
StructType=TFib, Comma
nd=ContainerCommand:[unknown CTCOMMAND:193]
 2665 -1210266784 IOCTL -- faos_SendReceiveFIB, Passed FSACTL_SENDFIB
 2665 -1210266784 FIB   <- faos_SendReceiveFIB with fd=4

The line:

 2665 -1210266784 FIB   -- faos_SendReceiveFIB: Size=464, 
StructType=TFib, Comma
nd=ContainerCommand:[unknown CTCOMMAND:193]

could be the culprit but I have no idea about what to do about it. Any 
insight from the members of this list?

Thanks!

Carlos



More information about the Linux-PowerEdge mailing list