Actions
Bug #52531
openQuotas smaller than 4MB on subdirs do not have any effect
% Done:
0%
Source:
Community (user)
Tags:
Backport:
pacific,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
This doesn’t work:
root@mon0:~# setfattr -n ceph.quota.max_bytes -v $((4*1024*1024-1)) /mnt/cephfs/
root@mon0:~# getfattr -n ceph.quota.max_bytes /mnt/cephfs/
getfattr: Removing leading '/' from absolute path names
root@mon0:~# setfattr -n ceph.quota.max_bytes -v $((4*1024*1024)) /mnt/cephfs/
root@mon0:~# getfattr -n ceph.quota.max_bytes /mnt/cephfs/
getfattr: Removing leading '/' from absolute path names
root@mon0:~# setfattr -n ceph.quota.max_bytes -v $((4*1024*1024-1)) /mnt/cephfs/
root@mon0:~# getfattr -n ceph.quota.max_bytes /mnt/cephfs/
getfattr: Removing leading '/' from absolute path names
- file: mnt/cephfs/
ceph.quota.max_bytes="4194303"
root@mon0:~# df -h /mnt/cephfs/
Filesystem Size Used Avail Use% Mounted on
192.168.42.10:6789,192.168.42.11:6789,192.168.42.12:6789:/subdir 28G 0 28G 0% /mnt/cephfs
The 28GB is the size of the parent fs.
But this does:root@mon0:~# setfattr -n ceph.quota.max_bytes -v $((4*1024*1024)) /mnt/cephfs/
root@mon0:~# getfattr -n ceph.quota.max_bytes /mnt/cephfs/
getfattr: Removing leading '/' from absolute path names
- file: mnt/cephfs/
ceph.quota.max_bytes="4194304"
root@mon0:~# df -h /mnt/cephfs/
Filesystem Size Used Avail Use% Mounted on
192.168.42.10:6789,192.168.42.11:6789,192.168.42.12:6789:/subdir 4.0M 0 4.0M 0% /mnt/cephfs
I did test this in both Octopus and Pacific
Updated by Patrick Donnelly over 2 years ago
- Status changed from New to Triaged
- Assignee set to Ramana Raja
- Target version set to v17.0.0
- Source set to Community (user)
- Backport set to pacific,octopus
- Component(FS) Client added
Actions