Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 2 February 8, 2022 Condition also occurs when FC Boot From SAN (BFS) is performed. 1 September 14, 2021 Original Document Release. On any HPE Synergy Compute Module running Red Hat Enterprise Linux 7 Server, Red Hat Enterprise Linux 8 Server, SUSE Linux Enterprise Server 12 or SUSE Linux Enterprise Server 15, and configured with either of the HPE Synergy Converged network adapters listed in the Scope section below; unexpected error messages similar to the following may be displayed when an iSCSI/FC Boot From SAN (BFS) with HPE 3PAR / Nimble Storage is performed to the Linux Operating System when multiple-path is configured: blk_update_request: I/O error, dev sdb, sector 109347248 op 0x1:(WRITE) flags 0x4a00 phys_seg 1 prio class 0 blk_update_request: I/O error, dev sdb, sector 21789848 op 0x0:(READ) flags 0x84700 phys_seg 18 prio class 0 blk_update_request: I/O error, dev sdb, sector 113690112 op 0x0:(READ) flags 0x84700 phys_seg 4 prio class 0 The iSCSI issue occurs because the DM layer calls blk_update_request() for partial completion handling for request-based multipath before it starts cloning this request to other active paths. The FC issue occurs because one or more of the active paths have gone down. These messages get printed in flight I/O and the Low Level Discovery (LLD) needs to retry. Important Information These messages above can be safely ignored in a multiple-path configuration only. Check if the device applies to a multiple-path device by performing command "multipath -ll" or "lsblk". The output of the command "multipath -ll" will show which SCSI/FC devices constitute a multipath device mapper volume. 360002ac000000000000002be0001c645 dm-0 3PARdata,VV size=100G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:1:0 sdd 8:48 active ready running `- 2:0:0:0 sdb 8:16 active ready running 360002ac000000000000002b40001c645 dm-4 3PARdata,VV size=20G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:1:1 sde 8:64 active ready running `- 2:0:0:1 sdc 8:32 active ready running The output of the command "lsblk" will show which SCSI/FC devices constitute a multipath device mapper volume. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:16 0 100G 0 disk +-sdb1 8:17 0 2G 0 part +-sdb2 8:18 0 4G 0 part +-sdb3 8:19 0 94G 0 part +-360002ac000000000000002be0001c645 254:0 0 100G 0 mpath +-360002ac000000000000002be0001c645-part1 254:1 0 2G 0 part /boot/efi +-360002ac000000000000002be0001c645-part2 254:2 0 4G 0 part [SWAP] +-360002ac000000000000002be0001c645-part3 254:3 0 94G 0 part / sdc 8:32 0 20G 0 disk +-sdc1 8:33 0 20G 0 part +-360002ac000000000000002b40001c645 254:4 0 20G 0 mpath +-360002ac000000000000002b40001c645-part1 254:5 0 20G 0 part /root/Desktop/Data sdd 8:48 0 100G 0 disk +-sdd1 8:49 0 2G 0 part +-sdd2 8:50 0 4G 0 part +-sdd3 8:51 0 94G 0 part +-360002ac000000000000002be0001c645 254:0 0 100G 0 mpath +-360002ac000000000000002be0001c645-part1 254:1 0 2G 0 part /boot/efi +-360002ac000000000000002be0001c645-part2 254:2 0 4G 0 part [SWAP] +-360002ac000000000000002be0001c645-part3 254:3 0 94G 0 part / sde 8:64 0 20G 0 disk +-sde1 8:65 0 20G 0 part +-360002ac000000000000002b40001c645 254:4 0 20G 0 mpath +-360002ac000000000000002b40001c645-part1 254:5 0 20G 0 part /root/Desktop/Data The same message where the SCSI/FC device is not part of a multipath should be immediately addressed, as it is warning of potential data loss.
Any HPE Synergy Compute Module running Red Hat Enterprise Linux 7 Server, Red Hat Enterprise Linux 8 Server, SUSE Linux Enterprise Server 12 or SUSE Linux Enterprise Server 15, and configured with either of the following HPE Synergy Converged network adapters: HPE Synergy 4820C 10/20/25Gb Converged Network Adapter (876449-B21) HPE Synergy 6820C 25/50Gb Converged Network Adapter (P02054-B21)
In case of iSCSI, the connection disruption is not an external entity (for example, a link event) and it occurs because the Open-iSCSI daemon starts running after a switch root, and iscsid tries to take control of iSCSI/FC connection; therefore, the I/Os continue to submit to the Low Level Discovery (LLD) queue. During this process, some I/Os are with the Low Level Discovery (LLD) before it starts to failover to other active paths, which need to be aborted; therefore, this message has no adverse effect on the system and it can be safely ignored. In case of FC, the connection disruption is an external entity (for example, a target port) and it occurs because one or more of the active paths to the storage failed. This message has no adverse effect on the system and it can be safely ignored. This message should be immediately addressed if it is occurring on a SCSI/FC device that is not part of a multipath configuration, as it is a warning of potential data loss. Determine the type of device that is causing the error and follow the standard troubleshooting practice for that device. Contact HPE Customer Support if assistance is needed. Click on the following URL to locate the HPE Customer Support phone number in your country: TECHNICAL SUPPORT PHONE NUMBERS RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches and other support software downloads, refer to the Navigation Tips document. SEARCH TIP: For hints on locating similar documents on HPE.com, refer to the Search Tips document.