Description of problem: Presently we have an issue about enabling quota with volume set command. This actually as per developers itself is not a correct way of enabling quota translator. As we already have gluster volume quota $volname enable command, hence request you to deprecate or warn people about the problem that they may face with enabling quota along with "volume set" command. Earlier also to avoid confusion we had filed a BZ 1001573 which was closed as NOTABUG
Patch posted for review on branch rhs-2.1 : https://code.engineering.redhat.com/gerrit/#/c/14827/ Patch posted for review on branch rhs-2.1-u1 : https://code.engineering.redhat.com/gerrit/#/c/14835/
Patch for rhs-2.1 posted on: https://code.engineering.redhat.com/gerrit/#/c/17725/ Upstream patch url: http://review.gluster.org/#/c/6512/
verified on glusterfs-3.4.0.52rhs-1.el6rhs [root@quota5 ~]# gluster volume set dist-rep quota enable volume set: failed: 'gluster volume set <VOLNAME> quota enable' is deprecated. Use 'gluster volume quota <VOLNAME> enable' instead. [root@quota5 ~]# gluster volume info dist-rep Volume Name: dist-rep Type: Distributed-Replicate Volume ID: 4ee792db-48f0-463e-8ad1-d1507d161227 Status: Started Number of Bricks: 6 x 2 = 12 Transport-type: tcp Bricks: Brick1: 10.70.35.219:/rhs/brick1/d1r1 Brick2: 10.70.35.108:/rhs/brick1/d1r2 Brick3: 10.70.35.191:/rhs/brick1/d2r1 Brick4: 10.70.35.144:/rhs/brick1/d2r2 Brick5: 10.70.35.219:/rhs/brick1/d3r1 Brick6: 10.70.35.108:/rhs/brick1/d3r2 Brick7: 10.70.35.191:/rhs/brick1/d4r1 Brick8: 10.70.35.144:/rhs/brick1/d4r2 Brick9: 10.70.35.219:/rhs/brick1/d5r1 Brick10: 10.70.35.108:/rhs/brick1/d5r2 Brick11: 10.70.35.191:/rhs/brick1/d6r1 Brick12: 10.70.35.144:/rhs/brick1/d6r2
Can you please verify if the doc text is technically correct?
Doc text is correct.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html