REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#1) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#2) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#3) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#4) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#5) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#6) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#7) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#8) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8439 (geo-rep: Fixing issue with xsync upper limit) posted (#9) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/8439 committed in master by Vijay Bellur (vbellur) ------ commit d0a3b4307e40b70d73faf4baed9fa0c930682894 Author: Aravinda VK <avishwan> Date: Fri Aug 8 15:06:11 2014 +0530 geo-rep: Fixing issue with xsync upper limit While identifying the file/dir to sync, xtime of the file was compared with xsync_upper_limit as `xtime < xsync_upper_limit` After the sync, xtime of parent directory is updated as stime. With the upper limit condition, stime is updated as MIN(xtime_parent, xsync_upper_limit) With this files will get missed if `xtime_of_file == xsync_upper_limit` With this patch xtime_of_file is compared as xtime_of_file <= xsync_upper_limit BUG: 1128093 Change-Id: I5022ce67ba503ed4621531a649a16fc06b2229d9 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/8439 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/8517 (features/changelog: barrier all entry creation fops) posted (#3) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8533 (features/changelog: Crash consistency of changelog wrt snapshot) posted (#1) for review on master by ajeet jha (ajha)
REVIEW: http://review.gluster.org/8533 (features/changelog: Crash consistency of changelog wrt snapshot) posted (#2) for review on master by ajeet jha (ajha)
COMMIT: http://review.gluster.org/8517 committed in master by Vijay Bellur (vbellur) ------ commit 11beb72ef0ec80d13dcfe7061b46cad105f6e77e Author: Vijay Bellur <vbellur> Date: Fri Aug 22 17:15:13 2014 +0530 features/changelog: barrier all entry creation fops when a snapshot is taken, there are chances of entry creation fops not being recorded either in changelog or through the recursive ancestry xtime updation by marker. This causes consumers of changelog (primarily geo-replication as of today) to not be aware of these entries after a snapshot is restored. This can lead to inconsistencies. This patch is an interim workaround to barrier creates till changelog becomes completely crash consistent. BUG: 1128093 Change-Id: Ie0dbfd74beecb88df5c2ddf9fc680af91547c3f3 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/8517 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: ajeet jha <ajha> Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Kotresh HR <khiremat>
REVIEW: http://review.gluster.org/8533 (features/changelog: Crash consistency of changelog wrt snapshot) posted (#3) for review on master by ajeet jha (ajha)
REVIEW: http://review.gluster.org/8533 (features/changelog: Crash consistency of changelog wrt snapshot) posted (#4) for review on master by ajeet jha (ajha)
REVIEW: http://review.gluster.org/8533 (features/changelog: Crash consistency of changelog wrt snapshot) posted (#5) for review on master by ajeet jha (ajha)
REVIEW: http://review.gluster.org/8542 (features/changelog: Removal of redundant fop color count while draining.) posted (#1) for review on master by ajeet jha (ajha)
COMMIT: http://review.gluster.org/8533 committed in master by Vijay Bellur (vbellur) ------ commit acabde2c297c4175946565017ba17a251ad3fb1c Author: Ajeet Jha <ajha> Date: Sat Aug 23 19:06:45 2014 +0530 features/changelog: Crash consistency of changelog wrt snapshot This patch introduces call-path fop details logging for data operations in CHANGELOG.SNAP. This feature is enabled with barrier-enable notification and disabled with barrier-disable notification. Change-Id: Ib548d34203eb99cea478a6baff402e82251c73a4 BUG: 1128093 Signed-off-by: Ajeet Jha <ajha> Reviewed-on: http://review.gluster.org/8533 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
COMMIT: http://review.gluster.org/8542 committed in master by Vijay Bellur (vbellur) ------ commit 27daeba0f7e02669919a7d89a04ea8fe39e06898 Author: Ajeet Jha <ajha> Date: Tue Aug 26 14:39:24 2014 +0530 features/changelog: Removal of redundant fop color count while draining. Change-Id: Ie5581579df63513e636fa3dd92dd90699ea7d999 BUG: 1128093 Signed-off-by: Ajeet Jha <ajha> Reviewed-on: http://review.gluster.org/8542 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user