we have the bug fix already in upstream. giving it a devel-ack. need to know when the fix will get in ? (ie, which errata update).
reducing the priority as the bug would not be hit when disk space on '/' partition is not full. Also, the fix is already upstream, so matter of deciding on the target 2.0.z release stream to backport it.
missed these from scrub. Should we target these for Update5? (as the flags mention 2.0.z vehicle).
This patch was got into rhs-2.1 from the upstream rebase - http://review.gluster.com/3726 This fix is certainly available in an earlier version than glusterfs-3.4.0.12rhs.beta4-1. But it makes sense to update a more recent version for ease of verification. Marking it ON_QA, with verified in glusterfs-3.4.0.12rhs.beta4-1
This issue is fixed in 2.1 Bug 851989 . Marking this as Closed CurrentRelease.