Dell Emulex Family of Adapters - Manual (Page 875)

Emulex Drivers Version 10.2 for Linux User Manual P010081-01A Rev. A
4. Troubleshooting
Situations and their Resolutions
875
rmmod fails to unload driver due to
device or resource busy. This message occurs when you attempt to remove the driver
without first stopping the OneCommand Manager application or
the fcauthd daemon when the OneCommand Manager
application is installed and running, or when FC disks
connected to a LightPulse adapter are mounted. To resolve this
situation:
1) Stop the OneCommand Manager application before
attempting to unload the driver. The script is located in the
/usr/sbin/ocmanager directory. Type
./stop_ocmanager
2) Unmount any disks connected to the adapter.
3) Unload the driver. Type
rmmod lpfc
An lspci shows recent Emulex adapters
as unknown. This situation occurs because of the delay of getting new
product IDs into the Linux development cycle.
There is no resolution at this time.
Slow targets or extended link faults on
the storage side may result in storage
being marked offline by the mid-level
and remaining offline (not recovered)
when the link faults are corrected. This version of the driver should eliminate this issue. However,
if you experience offline device issues, increase the SCSI
command timeout to a value greater than or equal to 60
seconds. Emulex also provides a script which addresses this
issue.
To access the lun_change_state.sh script, go to
http://www.emulex.com/files/downloads/linux/tools.html.
Under certain conditions of an I/O
load, some targets cannot complete an
I/O issued by a Linux initiator within
the default timeout of 30 seconds
given by the SCSI mid-level. If the situation is not corrected, the initiator-to-target
condition deteriorates into abort/recovery storms, leading to
I/O failures in the block layer. These types of failures are
preceded by a SCSI I/O error of hex 6000000.
Emulex provides a script that addresses this issue.
To access the set_target_timeout.sh script, go to
http://www.emulex.com/files/downloads/linux/tools.html.
The FC or FCoE driver fails to
recognize an adapter and logs
“unknown IOCB” messages in the
system log during driver load. The adapter is running outdated firmware.
Install the latest firmware on the adapter.
Note: Before performing a firmware update, driver installation
is required. See “Installing the Binary RPM FC and FCoE
Driver Kit” on page 816.
Loading the FC and FCoE driver on
SLES 11 SPx reports “unsupported
module, tainting kernel” in system log. This message is logged by the kernel whenever a module that is
not shipped with the kernel is loaded.
This message can be ignored.
The system panics when it is booted
with a failed adapter installed. Remove the failed adapter and reboot the system.
Table 4-1 FC and FCoE Driver Situations and their Resolutions (Continued)
Situation Resolution