Description of problem: I just tried to set limit on long path and brick went down [root@quota1 ~]# gluster volume info Volume Name: dist-rep Type: Distributed-Replicate Volume ID: b1b80b68-b98b-4aab-a563-3c386c39b842 Status: Started Number of Bricks: 6 x 2 = 12 Transport-type: tcp Bricks: Brick1: 10.70.37.98:/rhs/bricks/d1r1 Brick2: 10.70.37.174:/rhs/bricks/d1r2 Brick3: 10.70.37.136:/rhs/bricks/d2r1 Brick4: 10.70.37.168:/rhs/bricks/d2r2 Brick5: 10.70.37.98:/rhs/bricks/d3r1 Brick6: 10.70.37.174:/rhs/bricks/d3r2 Brick7: 10.70.37.136:/rhs/bricks/d4r1 Brick8: 10.70.37.168:/rhs/bricks/d4r2 Brick9: 10.70.37.98:/rhs/bricks/d5r1 Brick10: 10.70.37.174:/rhs/bricks/d5r2 Brick11: 10.70.37.136:/rhs/bricks/d6r1 Brick12: 10.70.37.168:/rhs/bricks/d6r2 Options Reconfigured: features.alert-time: 20s features.quota: on Version-Release number of selected component (if applicable): [root@quota1 ~]# rpm -qa | grep glusterfs glusterfs-3.4.0.12rhs.beta3-1.el6rhs.x86_64 glusterfs-fuse-3.4.0.12rhs.beta3-1.el6rhs.x86_64 glusterfs-debuginfo-3.4.0.12rhs.beta3-1.el6rhs.x86_64 glusterfs-server-3.4.0.12rhs.beta3-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1.[root@quota1 ~]# gluster volume quota dist-rep limit-usage /dirn/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 1GB hard limit set on /dirn/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 2. 3. Actual results: [root@quota1 ~]# gluster volume status Status of volume: dist-rep Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.37.98:/rhs/bricks/d1r1 49152 Y 2404 Brick 10.70.37.174:/rhs/bricks/d1r2 49152 Y 18604 Brick 10.70.37.168:/rhs/bricks/d2r2 49152 Y 7692 Brick 10.70.37.98:/rhs/bricks/d3r1 49153 Y 2417 Brick 10.70.37.174:/rhs/bricks/d3r2 49153 Y 18615 Brick 10.70.37.168:/rhs/bricks/d4r2 49153 Y 7703 Brick 10.70.37.98:/rhs/bricks/d5r1 49154 Y 2428 Brick 10.70.37.174:/rhs/bricks/d5r2 49154 Y 18626 Brick 10.70.37.168:/rhs/bricks/d6r2 49154 Y 7714 NFS Server on localhost 2049 Y 2442 Self-heal Daemon on localhost N/A Y 2448 NFS Server on d6203fcb-6e40-417e-986b-6a74c7f23c42 2049 Y 7728 Self-heal Daemon on d6203fcb-6e40-417e-986b-6a74c7f23c4 2 N/A Y 7737 NFS Server on cc7bc8ba-fa3a-43d9-a899-114e34d27eb4 2049 Y 18639 Self-heal Daemon on cc7bc8ba-fa3a-43d9-a899-114e34d27eb 4 N/A Y 18650 on machine 10.70.37.139, brick is down with a crash, [root@quota1 ~]# gluster volume quota dist-rep list Path Hard-limit Soft-limit Used Available -------------------------------------------------------------------------------- / 20GB 90% 16384.0PB 20.0GB /dir1/dir-1 1GB 90% N/A N/A /dir1/dir-2 1GB 90% N/A N/A /dir1/dir-3 1GB 90% N/A N/A /dir1/dir-4 1GB 90% N/A N/A /dir1/dir-5 1GB 90% N/A N/A /dir1/dir-6 1GB 90% N/A N/A /dir1/dir-7 1GB 90% N/A N/A /dir1/dir-8 1GB 90% N/A N/A /dir1/dir-9 1GB 90% N/A N/A /dir1 10GB 90% 0Bytes 10.0GB /dir1/dir-10 1GB 90% N/A N/A /dir/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 1GB 90% N/A N/A /dirn/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10 1GB 90% N/A N/A [root@quota1 ~]# Expected results: the bricks should stay alive, and quota limit set should be allowed on any path Additional info:
keeping it as 'high' priority as its about crash. patch merged into downstream. Next beta build would have it.
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/RHBA-2013-1262.html