Steffen, > Kernel message explanation: > > * Description: > * The FCP channel reported that its bit error threshold has been exceeded. > * These errors might result from a problem with the physical components > * of the local fibre link into the FCP channel. > * The problem might be damage or malfunction of the cable or > * cable connection between the FCP channel and > * the adjacent fabric switch port or the point-to-point peer. > * Find details about the errors in the HBA trace for the FCP device. > * The zfcp device driver closed down the FCP device > * to limit the performance impact from possible I/O command timeouts. > * User action: > * Check for problems on the local fibre link, ensure that fibre optics are > * clean and functional, and all cables are properly plugged. > * After the repair action, you can manually recover the FCP device by > * writing "0" into its "failed" sysfs attribute. > * If recovery through sysfs is not possible, set the CHPID of the device > * offline and back online on the service element. This commentary does not read like a patch description. It makes no mention of the actual kernel changes and the introduced module parameter. > +static bool ber_stop = true; > +module_param(ber_stop, bool, 0600); > +MODULE_PARM_DESC(ber_stop, > + "Shuts down FCP devices for FCP channels that report a bit-error count in excess of its threshold (default on)"); > + -- Martin K. Petersen Oracle Linux Engineering
