Bug 1488103 - Rebalance fails on NetBSD because fallocate is not implemented
Summary: Rebalance fails on NetBSD because fallocate is not implemented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1516691 1520232
TreeView+ depends on / blocked
 
Reported: 2017-09-04 10:39 UTC by Pranith Kumar K
Modified: 2018-03-15 11:17 UTC (History)
3 users (show)

Fixed In Version: glusterfs-4.0.0
Clone Of:
: 1516691 1520232 (view as bug list)
Environment:
Last Closed: 2018-03-15 11:17:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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/


Note You need to log in before you can comment on or make changes to this bug.