Bug 1342372
Summary: | [quota+snapshot]: Directories are inaccessible from activated snapshot, when the snapshot was created during directory creation | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Mohammed Rafi KC <rkavunga> | |
Component: | snapshot | Assignee: | Mohammed Rafi KC <rkavunga> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.8.0 | CC: | bugs, kramdoss, nbalacha, rcyriac, rhinduja, rjoseph, rkavunga | |
Target Milestone: | --- | Keywords: | Regression, ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8.0 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1341796 | |||
: | 1342374 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 12:33:36 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: | 1341034, 1341796 | |||
Bug Blocks: | 1311817, 1342374, 1342375 |
Description
Mohammed Rafi KC
2016-06-03 06:10:35 UTC
REVIEW: http://review.gluster.org/14628 (glusterd/snapshot: remove quota related options from snap volfile) posted (#1) for review on release-3.8 by mohammed rafi kc (rkavunga) COMMIT: http://review.gluster.org/14628 committed in release-3.8 by Atin Mukherjee (amukherj) ------ commit f4869c33489a79a79ae04f40b1711932fbee15e6 Author: Mohammed Rafi KC <rkavunga> Date: Wed Jun 1 23:01:37 2016 +0530 glusterd/snapshot: remove quota related options from snap volfile enabling inode-quota on a snapshot volume is unnecessary, because snapshot is a read-only volume. So we don't need to enforce quota on a snapshot volume. This patch will remove the quota related options from snapshot volfile. Backport of> >Change-Id: Iddabcb83820dac2384924a01d45abe1ef1e95600 >BUG: 1341796 >Signed-off-by: Mohammed Rafi KC <rkavunga> >Reviewed-on: http://review.gluster.org/14608 >Reviewed-by: Atin Mukherjee <amukherj> >Reviewed-by: N Balachandran <nbalacha> >NetBSD-regression: NetBSD Build System <jenkins.org>> >Smoke: Gluster Build System <jenkins.com> >CentOS-regression: Gluster Build System <jenkins.com> >Reviewed-by: Rajesh Joseph <rjoseph> (cherry picked from commit 03d523504230c336cf585159266e147945f31153) Change-Id: I68b54cc3e9a5420d6b3550b08fd65c3c44a130cf BUG: 1342372 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/14628 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Rajesh Joseph <rjoseph> CentOS-regression: Gluster Build System <jenkins.com> 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-3.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |