Bug 1632717

Summary:	EC crashes when running on non 64-bit architectures
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	porting	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:30:59 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:

Description Xavi Hernandez 2018-09-25 11:22:29 UTC

Description of problem:

When gluster is compiled on a non 64-bit architecture, it shows many warnings, but creates an executable. However that executable doesn't work when a disperse volume is created.


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


How reproducible:

Always

Steps to Reproduce:
1. Compile gluster in a 32 bit architecture
2. Create a dispersed volume
3. Try to create a file and write data to it

Actual results:

The fuse mount crashes

Expected results:

The file should be created and written.

Additional info:

Some of the warnings are critical because of the implied size of size_t data type when passed as a reference to some functions that expect an uint64_t *.

Comment 1 Worker Ant 2018-09-25 12:20:52 UTC

REVIEW: https://review.gluster.org/21276 (all: fix warnings on non 64-bits architectures) posted (#1) for review on master by Xavi Hernandez

Comment 2 Worker Ant 2018-10-10 05:51:05 UTC

COMMIT: https://review.gluster.org/21276 committed in master by "Amar Tumballi" <amarts> with a commit message- all: fix warnings on non 64-bits architectures

When compiling in other architectures there appear many warnings. Some
of them are actual problems that prevent gluster to work correctly on
those architectures.

Change-Id: Icdc7107a2bc2da662903c51910beddb84bdf03c0
fixes: bz#1632717
Signed-off-by: Xavi Hernandez <xhernandez>

Comment 3 Shyamsundar 2019-03-25 16:30:59 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/