Bug 1513258 - NetBSD port
Summary: NetBSD port
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: porting
Version: 3.12
Hardware: All
OS: NetBSD
unspecified
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-15 02:57 UTC by manu@netbsd.org
Modified: 2017-12-19 07:17 UTC (History)
1 user (show)

Fixed In Version: glusterfs-glusterfs-3.12.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1129939
Environment:
Last Closed: 2017-12-19 07:17:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description manu@netbsd.org 2017-11-15 02:57:03 UTC
+++ This bug was initially created as a clone of Bug #1129939 +++

This bug is a placeholder to gather change sets for porting GlusterFS release-3.12 branch to NetBSD

Comment 1 Worker Ant 2017-11-15 03:08:14 UTC
REVIEW: https://review.gluster.org/18782 (Disable gfid2path by default on NetBSD) posted (#1) for review on release-3.12 by Emmanuel Dreyfus

Comment 2 Worker Ant 2017-11-15 03:14:01 UTC
REVIEW: https://review.gluster.org/18778 (Disable gfid2path by default on NetBSD) posted (#2) for review on release-3.12 by Emmanuel Dreyfus

Comment 3 Worker Ant 2017-12-08 14:39:20 UTC
COMMIT: https://review.gluster.org/18782 committed in release-3.12 by \"Emmanuel Dreyfus\" <manu> with a commit message- Disable gfid2path by default on NetBSD

NetBSD storage of extended attributes for UFS1 badly scales when
the list of extended attributes names rises. gfid2path can add as
many extended attributes names as we have files, hence we keep it
disabled for performance sake.

> Change-Id: Id77b5f5ceb4d5eba1b3362b4b9fc693450ffbc2b
> Signed-off-by: Emmanuel Dreyfus <manu>
> BUG: 1129939

Change-Id: Id77b5f5ceb4d5eba1b3362b4b9fc693450ffbc2b
Signed-off-by: Emmanuel Dreyfus <manu>
BUG: 1513258

Comment 4 Jiffin 2017-12-19 07:17:49 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-glusterfs-3.12.4, please open a new bug report.

glusterfs-glusterfs-3.12.4 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/gluster-devel/2017-December/054093.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.