Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 744811 - Non-responsive scsi target leads to excessive scsi recovery and dm-mp failover time [rhel-6.1.z]
Non-responsive scsi target leads to excessive scsi recovery and dm-mp failove...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Frantisek Hrbata
Gris Ge
: Reopened, ZStream
Depends On: 691945
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-10 10:56 EDT by RHEL Product and Program Management
Modified: 2013-01-10 23:03 EST (History)
13 users (show)

See Also:
Fixed In Version: kernel-2.6.32-131.20.1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-11-22 11:52:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1465 normal SHIPPED_LIVE Important: kernel security and bug fix update 2011-11-22 16:45:37 EST

  None (edit)
Description RHEL Product and Program Management 2011-10-10 10:56:13 EDT
This bug has been copied from bug #691945 and has been proposed
to be backported to 6.1 z-stream (EUS).
Comment 6 Gris Ge 2011-11-13 22:24:29 EST
4 hours I/O stress with FC faults on qla2xxx PASS.

Patch found in kernel-2.6.32-131.20.1.el6

Sanity Only
Comment 7 errata-xmlrpc 2011-11-22 11:52:06 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2011-1465.html

Note You need to log in before you can comment on or make changes to this bug.