Stripe functionality has been implemented by sharding. The stripe xlator is barely maintained anymore and should be deprecated. The plan is to remove the stripe xlator in two steps: 1. remove the command line option to prevent users from creating new volumes that use the stripe xlator 2. after a release that includes point 1, remove the stripe xlator from the sources This bug deals with point 2, the first step is done in bug 1364706.
https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html talks about deprecation, and hence we can technically remove all the code for stripe from codebase (including tests)
https://review.gluster.org/21327
REVIEW: https://review.gluster.org/21433 (stripe: remove the translator from build and glusterd) posted (#9) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/21433 (stripe: remove the translator from build and glusterd) posted (#10) for review on master by Atin Mukherjee
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/