Bug 1508661 - Failure to set quota on root directory of empty disperse volume that has attached hot tier.
Summary: Failure to set quota on root directory of empty disperse volume that has atta...
Keywords:
Status: CLOSED DUPLICATE of bug 1408359
Alias: None
Product: GlusterFS
Classification: Community
Component: quota
Version: 3.12
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Sanoj Unnikrishnan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-01 22:46 UTC by vnosov
Modified: 2017-11-13 17:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-10 05:42:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Step-by-step procedure to reproduce the bug. (12.31 KB, text/plain)
2017-11-01 22:46 UTC, vnosov
no flags Details

Description vnosov 2017-11-01 22:46:42 UTC
Created attachment 1346789 [details]
Step-by-step procedure to reproduce the bug.

Description of problem: Create disperse volume, attach hot tier to the volume,
enable directory quotas on the volume, set quota on root directory of the volume, check quotas list of the volume. The response lists root directory but all settings have value "N/A".  


Version-Release number of selected component (if applicable): GlusterFS 3.12.2


How reproducible: 100%


Steps to Reproduce: See the attachment.
1.
2.
3.

Actual results:
The quota settings are not available if quota command "list" is used.


Expected results:
Have to see the quota settings that were submitted.


Additional info:

After the volume is mounted locally, create directory in the root. In-mount the volume. Set quota on the volume root directory again.  The created quota is listed properly now. Have to have this without mounting/making changes/un-mounting the volume. See the attachment.

Comment 1 Sanoj Unnikrishnan 2017-11-03 10:13:59 UTC
This seems to be a duplicate of 1408359. 
IMO, The limit is set correctly however not listed.
you can verify that the limit has been set on the root directory by doing a getfattr -d -m. -e hex <brick path>
u should get a line with "limit-set" as follows if the limit is set correctly.
trusted.glusterfs.quota.limit-set.1=0x...

@vnosov Please close this bug as a duplicate if u agree
 
It was considered lower priority as it gets resolved as soon as any operation takes place on root volume.

Comment 2 Sanoj Unnikrishnan 2017-11-10 05:42:59 UTC
Marking as duplicate as per above comment

*** This bug has been marked as a duplicate of bug 1408359 ***


Note You need to log in before you can comment on or make changes to this bug.