| Summary: | After healing different quota-sizes are seen on export directories of a replicate subvolume | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Raghavendra G <raghavendra> |
| Component: | quota | Assignee: | Raghavendra G <raghavendra> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | amarts, gluster-bugs, rabhat, vijay |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTNR | Mount Type: | fuse |
| Documentation: | DNR | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Raghavendra Bhat
2011-04-11 03:11:16 UTC
root@booradley:/home/raghu/work/git/glusterfs# ./extras/quota-metadata-cleanup.sh /home/export/[56] && getfattr -e hex /home/export/[56]// -n trusted.glusterfs.quota.size && find /mnt/glusterfs | xargs touch && ./extras/quota-metadata-cleanup.sh /home/export/[56] && find /mnt/raghu | xargs touch && getfattr -e hex /home/export/[56]// -n trusted.glusterfs.quota.size /home/export/5/: trusted.glusterfs.quota.size: No such attribute /home/export/6/: trusted.glusterfs.quota.size: No such attribute getfattr: Removing leading '/' from absolute path names # file: home/export/5/ trusted.glusterfs.quota.size=0x0000000005180dfa # file: home/export/6/ trusted.glusterfs.quota.size=0x0000000005686567 However the disk-usage is same: root@booradley:/home/raghu/work/git/glusterfs# du -hs /home/export/5 396M /home/export/5 root@booradley:/home/raghu/work/git/glusterfs# du -hs /home/export/6 396M /home/export/6 Also note that the size as indicated by xattrs (around 84MB) is not the same as shown by du. regards, Raghavendra. Tried the same test with tag v3.2.0qa12, and everything seems to be working fine. Can some one in QA too confirm this is fixed. Tested on top of fixes to bug 764429 and everything is working fine. Hence marking this bug as resolved. |