Bug 1017728
Summary: | quota: decimal digits not shown properly for "df -h" | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> |
Component: | quota | Assignee: | Susant Kumar Palai <spalai> |
Status: | CLOSED NOTABUG | QA Contact: | storage-qa-internal <storage-qa-internal> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | grajaiya, mzywusko, rhs-bugs, storage-qa-internal, vagarwal, vbellur, vmallika |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
On setting the quota limit as a decimal digit and setting the deem-statfs on, a difference is noticed in the values displayed by the df -h command and gluster volume quota <volname> list command. In case of the gluster volume quota <volname> list command, the values do not get rounded off to the next integer.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-01-12 09:05:32 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: | |||
Bug Blocks: | 1020127 |
Description
Saurabh
2013-10-10 11:59:58 UTC
Per bug triage 10/17. The quota command shows values which are more precise then df does and hence this should not be considered a bug. Yes it is different, but as far as it is not wrong (more correct in this case), we should be fine. Unless I have missed something, this should not be called a bug at all, or I must be missing something This is an important bug, not sure whether we want to take it for "U1" or not. The importance of this can be understood by the use case I mention below, " A combination of quota-deem-statfs, quota is used for standard tools like df to represent the actual size allocated to a directory." Now, a directory can be decimal digits as well, lets "1.5TB" or "2.5TB" Now, a non-root user(on some other node) will not be having access to a server to check the quota limit using "gluster volume quota $volname list" command. He can only use df -h. Now with this bug, a non-root user(on some other node) will be having impression of having "3TB" in case of 2.5TB, which literally can mess up the things. In fact, "df -h" to show quota limits set is required is because of one of the reasons that I have mentioned above, i.e. nodes other then RHSS can check the quota limits. So giving a wrong information will not be a good idea. I've documented this as a known issue in the Big Bend Update 1 Release Notes. Here is the link: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Storage/2.1/html/2.1_Update_1_Release_Notes/chap-Documentation-2.1_Update_1_Release_Notes-Known_Issues.html The issue is not with the quota. This is with 'df application'. To get the accurate value, run df command without '-h' option. Closing as 'NOTABUG' |