Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1569457 - EIO errors on some operations when volume has mixed brick versions on a disperse volume
EIO errors on some operations when volume has mixed brick versions on a dispe...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: disperse (Show other bugs)
3.4
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: Xavi Hernandez
Upasana
:
Depends On: 1566732
Blocks: 1503137
  Show dependency treegraph
 
Reported: 2018-04-19 06:03 EDT by Xavi Hernandez
Modified: 2018-09-04 02:47 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.12.2-13
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1566732
Environment:
Last Closed: 2018-09-04 02:46:03 EDT
Type: Bug
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-2018:2607 None None None 2018-09-04 02:47 EDT

  None (edit)
Description Xavi Hernandez 2018-04-19 06:03:43 EDT
+++ This bug was initially created as a clone of Bug #1566732 +++

Description of problem:

If a disperse volume has different brick versions, some operations done on the volume will generate EIO errors.

Version-Release number of selected component (if applicable): mainline


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 6 nchilaka 2018-05-16 08:45:33 EDT
Xavi,
can you help me with validation procedure.
1)What fops exactly were failing before fix
2)also when you are telling different brick version, are you refering to trusted.ec.version or the glusterfs version?
Comment 24 errata-xmlrpc 2018-09-04 02:46:03 EDT
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/RHSA-2018:2607

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