Bug 764985 (GLUSTER-3253)

Summary:	Files written to glusterFS mount read back as binary
Product:	[Community] GlusterFS	Reporter:	Timothy <timothy.carr>
Component:	stripe	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.2	CC:	amarts, gluster-bugs, rahulcs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	fuse
Documentation:	---	CRM:
Verified Versions:	3.2 branch	Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Amar Tumballi 2011-07-26 08:54:10 UTC

Hi Timoty,

Yes, we know that it is an issue with quick-read. Currently in 3.2.x branch the issue is not fixed, but the development tree (branch for release 3.3.0) has the fix. We will evaluate when the fix will be available in 3.2.x branch.

Regards,
Amar

Comment 1 Timothy 2011-07-26 11:48:16 UTC

Dear Gluster Dev Support Team, 

Thank you for a great product. 

Backend: Scientific Linux 5.4 X86_64, Intel Quad Core, 16gb RAM
App Version: gLuster 3.2.2 
Network; 1gigE
Servers: 8 Servers with 8 bricks for the distributed striped volume. 

This morning I noticed that our GlusterFS started to act a bit strange when writing files to the glusterFS mount. 

I wrote a few text files to the gluster mount and reading the files produced a binary output. Somehow the files had been converted to binary when read back. 

echo "timothy" > testfile
vi /mnt/gluster/testfile ( this produced the output of " ^@^@^@^@^@^@^@^@^@^@^@ " ) 
od -x /mnt/gluster/testfile ( produced the output of "0000000")

Some of the bricks contained more information in the file than others. This has to do with the striped volume. 

I then continued, with very good advice from the IRC channel on freenode, to disable a option on the volume called " gluster volume set <volname> performance.quick-read off ". I assume this is the translator for performance.quick-read. 

Immediately upon disabling the quick-read option on the volume I was able to read the data. 

Thanks 

Timothy Carr
University of Cape Town

Comment 2 Anand Avati 2011-07-27 06:20:14 UTC

CHANGE: http://review.gluster.com/111 (also do some cleanups) merged in release-3.2 by Anand Avati (avati)

Comment 3 Amar Tumballi 2011-07-27 06:25:08 UTC

fix already exists in master branch. Also its now pushed to release-3.2 branch. In release-3.1 branch we don't want anything because these xattr aggregation logic came with the marker translator (ie, only in code after release-3.2).

Comment 4 Timothy 2011-07-27 07:47:55 UTC

awesome. Thanks so much for the hard work. I will put to the test 

Cheers 
Timothy

Comment 5 Rahul C S 2011-08-19 03:00:44 UTC

Works fine with both quick-read on & off.