Abstract: An indication of an event is received at a storage controller. The indication of the event corresponds to a first severity. It is determined that the event is associated with a first stream of commands. It is determined whether the indication of the event is the first indication of the event received by the storage controller. If the indication of the event is the first indication of the event received by the storage controller, a maximum allowed count of in-flight commands to be less than a current count of in-flight commands is set. If the indication of the event is not the first indication of the event received by the storage controller, it is determined that the first severity is greater than a second severity corresponding to a previously received indication. If the first severity is greater than the second severity, the maximum allowed count of in-flight commands is decreased.

Abstract: An indication of an event occurrence is received. The indication of the event occurrence is associated with a severity. A tag associated with the indication of the event occurrence is determined. It is determined whether the tag is the same as a preceding tag. In response to a determination that the tag is not the same as the preceding tag, a component is notified of the event occurrence, the tag is stored for later use, and an indication of the severity associated with the indication of the event occurrence is stored.

Abstract: An indication of an event is received at a storage controller. The indication of the event corresponds to a first severity. It is determined that the event is associated with a first stream of commands. It is determined whether the indication of the event is the first indication of the event received by the storage controller. If the indication of the event is the first indication of the event received by the storage controller, a maximum allowed count of in-flight commands to be less than a current count of in-flight commands is set. If the indication of the event is not the first indication of the event received by the storage controller, it is determined that the first severity is greater than a second severity corresponding to a previously received indication. If the first severity is greater than the second severity, the maximum allowed count of in-flight commands is decreased.

Abstract: An indication of an event occurrence is received. The indication of the event occurrence is associated with a severity. A tag associated with the indication of the event occurrence is determined. It is determined whether the tag is the same as a preceding tag. In response to a determination that the tag is not the same as the preceding tag, a component is notified of the event occurrence, the tag is stored for later use, and an indication of the severity associated with the indication of the event occurrence is stored.

Abstract: Some aspects of the disclosure describe a method for testing a storage controller by emulating storage area network (SAN) topologies and vendor-specific behavior in the storage controller. The method can include detecting, via a processor in the storage controller, a physical storage device connected to the storage controller. In response to detecting the physical storage device, the method can determine logic unit numbers (LUNs) based on device characteristics of the physical storage device, and determine a SAN topology to emulate, wherein the SAN topology defines paths leading to the LUNs. The method can also include updating, via the processor, configuration information used by components of the storage controller to indicate the paths leading to the LUNs. The method can also include detecting an input/out request that requires data associated with the LUNs. The method can also include determining, using the configuration information, the data associated with the LUNs.

Abstract: Method and system for handling error events on a current path for processing an I/O request for reading information from and writing information to a storage space is provided. A system is able to communicate with the storage space via more than one path. If the current path reports an error event, then an alternate path quality is determined to ascertain whether the alternate path will generate an error similar to the current path. The alternate path quality is determined based on a plurality of factors which are assigned certain weights. The weights are determined based on a likely contribution of each factor to a repetition of the error reported by the current path. If the alternate path quality is equal to or exceeds a programmable threshold value, then the alternate path is selected.

Abstract: Method and system for handling error events on a current path for processing an I/O request for reading information from and writing information to a storage space is provided. A system is able to communicate with the storage space via more than one path. If the current path reports an error event, then an alternate path quality is determined to ascertain whether the alternate path will generate an error similar to the current path. The alternate path quality is determined based on a plurality of factors which are assigned certain weights. The weights are determined based on a likely contribution of each factor to a repetition of the error reported by the current path. If the alternate path quality is equal to or exceeds a programmable threshold value, then the alternate path is selected.

Abstract: Lun communications between a storage server and a storage subsystem for a particular lun are assigned both a current path and an alternate path. Lun communications use the current path unless the current path is determined to be faulty. Path errors may result in the storage server determining a path to be faulty. If the current path for a lun communication is determined to be faulty, then the lun communications will be sent through the alternate path so long as the alternate path is determined to be reliable. Over time, a path previously determined to be faulty may recover and be used again for lun communications.