[Bug 207247] GEOM multip
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Feb 16 13:15:25 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207247
Bug ID: 207247
Summary: GEOM multip
Product: Base System
Version: 10.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: crest at bultmann.eu
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
GEOM multipath cycles through all paths to a device without remembering
previous path failures or differentiating between path and medium errors as
mentioned in #178473. I had a device fail during a planned clean power cycle
with this result:
GEOM_MULTIPATH: Error 5, da22 in jbod2data35 marked FAIL
GEOM_MULTIPATH: all paths in jbod2data35 were marked FAIL, restore da68
GEOM_MULTIPATH: da68 is now active path in jbod2data35
(da68:mps1:0:99:0): READ(10). CDB: 28 00 02 00 06 00 00 01 00 00
(da68:mps1:0:99:0): CAM status: SCSI Status Error
(da68:mps1:0:99:0): SCSI status: Check Condition
(da68:mps1:0:99:0): SCSI sense: MEDIUM ERROR asc:11,1 (Read retries exhausted)
(da68:mps1:0:99:0): Info: 0x2000654
(da68:mps1:0:99:0): Actual Retry Count: 63
(da68:mps1:0:99:0): Error 5, Unretryable error
GEOM_MULTIPATH: Error 5, da68 in jbod2data35 marked FAIL
GEOM_MULTIPATH: all paths in jbod2data35 were marked FAIL, restore da22
GEOM_MULTIPATH: da22 is now active path in jbod2data35
(da22:mps0:0:40:0): READ(10). CDB: 28 00 02 00 06 00 00 01 00 00
(da22:mps0:0:40:0): CAM status: SCSI Status Error
(da22:mps0:0:40:0): SCSI status: Check Condition
(da22:mps0:0:40:0): SCSI sense: MEDIUM ERROR asc:11,1 (Read retries exhausted)
(da22:mps0:0:40:0): Info: 0x2000654
(da22:mps0:0:40:0): Actual Retry Count: 63
(da22:mps0:0:40:0): Error 5, Unretryable error
GEOM_MULTIPATH: Error 5, da22 in jbod2data35 marked FAIL
GEOM_MULTIPATH: all paths in jbod2data35 were marked FAIL, restore da68
GEOM_MULTIPATH: da68 is now active path in jbod2data35
The system is stuck in the boot process in an endless loop over all paths to
the failed device.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list