Bug 1488103

Summary:	Rebalance fails on NetBSD because fallocate is not implemented
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	distribute	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nbalacha, rgowdapp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1516691 1520232 (view as bug list)		Environment:
Last Closed:	2018-03-15 11:17:56 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:	1516691, 1520232

Description Pranith Kumar K 2017-09-04 10:39:47 UTC

Description of problem:
We discovered a bug with rebalance while trying to get https://review.gluster.org/17746 patch merged. We found that NetBSD doesn't have support for fallocate so rebalance will fail. We need to handle fallocate failures gracefully and provide rebalance support even when fallocate is not supported.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-10-25 12:01:40 UTC

REVIEW: https://review.gluster.org/18573 (cluster/dht: make rebalance use truncate incase) posted (#1) for review on master by Susant Palai (spalai)

Comment 2 Worker Ant 2017-11-22 11:25:52 UTC

COMMIT: https://review.gluster.org/18573 committed in master by \"Susant Palai\" <spalai> with a commit message- cluster/dht: make rebalance use truncate incase

..
the brick file system does not support fallocate.

Change-Id: Id76cda2d8bb3b223b779e5e7a34f17c8bfa6283c
BUG: 1488103
Signed-off-by: Susant Palai <spalai>

Comment 3 Shyamsundar 2018-03-15 11:17:56 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-4.0.0, please open a new bug report.

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