[Bugs] [Bug 1360174] IO error seen with Rolling or non-disruptive upgrade of an distribute-disperse (EC) volume from 3.1.2 to 3.1.3
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jul 27 05:51:23 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1360174
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/15013 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com)
------
commit 197bbc9d150554b333504cc9616aaa19b937a8a6
Author: Ashish Pandey <aspandey at redhat.com>
Date: Fri Jun 17 17:52:56 2016 +0530
cluster/ec: Handle absence of keys in some callback dict
Problem: This issue arises when we do a rolling update
from 3.7.5 to 3.7.9.
For 4+2 volume running 3.7.5, if we update 2 nodes
and after heal completion kill 2 older nodes, this
problem can be seen. After update and killing of
bricks, 2 nodes will return inodelk count key in dict
while other 2 nodes will not have inodelk count in dict.
This is also true for get-link-count.
During dictionary match , ec_dict_compare, this will
lead to mismatch of answers and the file operation
on mount point will fail with IO error.
Solution:
Don't match inode, entry and link count keys while
comparing two dictionaries. However, while combining the
data in ec_dict_combine, go through all the dictionaries
and select the maximum values received in different dicts
for these keys.
master -
http://review.gluster.org/#/c/14761/
Change-Id: I33546e3619fe8f909286ee48fb0df2009cd3d22f
BUG: 1360174
Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Reviewed-on: http://review.gluster.org/14761
Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
Smoke: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Reviewed-on: http://review.gluster.org/15013
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YHKD4YuoLb&a=cc_unsubscribe
More information about the Bugs
mailing list