Bug 1040494

Summary:	Volume unmountable when performance.cache-size is set over 4GB
Product:	[Community] GlusterFS	Reporter:	Mark Janssen <mark>
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.2	CC:	bugs, gluster-bugs, iesool
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:	2015-10-07 13:49:43 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 Mark Janssen 2013-12-11 14:15:18 UTC

Description of problem:

When setting a performance.cache-size of 4GB or bigger on a volume, this volume becomes unmountable on the client(s) (with fuse-client)


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

3.4.2


How reproducible:

Always



Steps to Reproduce:
1. gluster volume set gv0 performance.cache-size 5GB
2. Umount volume on a client
3. Try to mount volume on a client

Actual results:
[2013-12-11 13:47:08.937425] E [io-cache.c:1572:check_cache_size_ok] 0-gv0-io-cache: Cache size 10737418240 is greater than the max size of 4017340416
Filesystem will not be mounted, above message is printed in the log

Expected results:
A mounted filesystem

Additional info:


Either do not allow setting a cache-size bigger then 4GB using the volume-set command, or mount the filesystem anyway (possibly still limiting the cache-size to 4GB).

Comment 1 Mark Janssen 2013-12-11 14:17:40 UTC

Also in my logs:
[2013-12-11 13:44:33.396125] W [options.c:148:xlator_option_validate_sizet] 0-gv0-io-cache: Cache size 42949672960 is out of range [4194304 - 34359738368]


Seems that there is a 32GB limit configured somewhere, but a 4GB limit is actually enforced/limiting.

I tried a 40GB cache-size... these systems have 64G, but i'm now running on 4GB

Comment 2 jiademing.dd 2014-01-12 05:16:17 UTC

I try the 3.4.1 and 3.4.2 ,I do gluster volume set xxx performance.cache-size 5GB or 10G, I can remount the client by fuse without error on the mathine which has 24G phy_memarys. 
I use Centos  2.6.32-220.el6.x86_64, What's your filesystem and your machine's phy-memary size?

Comment 3 Niels de Vos 2015-05-17 22:00:33 UTC

GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.

This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs".

If there is no response by the end of the month, this bug will get automatically closed.

Comment 4 Kaleb KEITHLEY 2015-10-07 13:49:43 UTC

GlusterFS 3.4.x has reached end-of-life.

If this bug still exists in a later release please reopen this and change the version or open a new bug.

Comment 5 Kaleb KEITHLEY 2015-10-07 13:50:53 UTC

GlusterFS 3.4.x has reached end-of-life.\                                                   \                                                                               If this bug still exists in a later release please reopen this and change the version or open a new bug.