Bug 1289447

Summary:	Sharding - Iozone on sharded volume fails on NFS
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	sharding	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1289570 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:49:19 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:
Bug Blocks:	1289570

Description Krutika Dhananjay 2015-12-08 07:15:26 UTC

Description of problem:

Same as "Summary".

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2015-12-08 07:34:06 UTC

REVIEW: http://review.gluster.org/12907 (features/shard: Do not update inode-ctx size (again) after xattrop) posted (#1) for review on master by Krutika Dhananjay (kdhananj)

Comment 2 Vijay Bellur 2015-12-08 21:46:45 UTC

COMMIT: http://review.gluster.org/12907 committed in master by Vijay Bellur (vbellur) 
------
commit 5fa88405ba1aba2312902255282fc4f6625d18ed
Author: Krutika Dhananjay <kdhananj>
Date:   Tue Dec 8 12:47:42 2015 +0530

    features/shard: Do not update inode-ctx size (again) after xattrop
    
    This is to fix race between parallel writevs that could mess up
    the file size value in inode ctx.
    
    Thanks to Pranith for helping with RCA'ing the issue.
    
    Change-Id: Ief94e0b3bcd87a8e2391fb39af1b99d020abd764
    BUG: 1289447
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/12907
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2016-06-16 13:49:19 UTC

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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user