Bug 1678785
Summary: | Loading table with too big physical size spams of type 6 VIO producing System Error -5 (plus soft lockup) | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jakub Krysl <jkrysl> | |
Component: | kmod-kvdo | Assignee: | corwin <corwin> | |
Status: | CLOSED ERRATA | QA Contact: | vdo-qe | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 8.0 | CC: | awalsh, bgurney, limershe, sweettea | |
Target Milestone: | rc | |||
Target Release: | 8.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 6.2.1.23 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1687005 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-05 22:12:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1682560 | |||
Bug Blocks: | 1687005 |
Description
Jakub Krysl
2019-02-19 15:18:52 UTC
# vdo create --name vdo --device /dev/sda Creating VDO vdo Starting VDO vdo Starting compression on VDO vdo VDO instance 2 volume is ready at /dev/mapper/vdo # dmsetup table vdo: 0 19487242776 vdo V2 /dev/disk/by-id/scsi-35000cca26c1a0a38 2441609216 4096 32768 16380 on auto vdo maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 # dmsetup suspend vdo # dmsetup reload vdo --table '0 19487242776 vdo V2 /dev/disk/by-id/scsi-35000cca26c1a0a38 2851209216 4096 32768 16380 on auto vdo maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1' # dmsetup suspend vdo # dmsetup resume vdo device-mapper: resume ioctl on vdo failed: Input/output error Command failed. syslog: [15577.848792] updateVIOErrorStats: 2038 callbacks suppressed [15577.848805] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176448 with error: System error -5 (-5) [15577.848808] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176384 with error: System error -5 (-5) [15577.848812] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176449 with error: System error -5 (-5) [15577.848814] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176512 with error: System error -5 (-5) [15577.848818] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176385 with error: System error -5 (-5) [15577.848822] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176513 with error: System error -5 (-5) [15577.848825] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176450 with error: System error -5 (-5) [15577.848828] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176451 with error: System error -5 (-5) [15577.848830] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176386 with error: System error -5 (-5) [15577.848832] kvdo2:journalQ: Completing write VIO of type 6 for physical block 2851176514 with error: System error -5 (-5) [15577.970134] kvdo2:dmsetup: resize operation failed, result = -5 [15577.976060] kvdo2:dmsetup: Commit of modifications to device 'vdo' failed: System error -5 (-5) [15577.984763] kvdo2:journalQ: Unrecoverable error, entering read-only mode: System error -5 (-5) [15577.993423] device-mapper: table: 253:0: vdo: preresume failed, error = -5 The spam is gone, only last 10 messages get printed. No more soft lockups because of that. Note: The number of callbacks suppressed is proportional to metadata size, not number of extra nonexistent physical blocks. 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. https://access.redhat.com/errata/RHBA-2019:3548 |