On Wed, Jul 26, 2017 at 1:03 PM Patrick Donnelly <pdonnell@xxxxxxxxxx> wrote:
On Wed, Jul 26, 2017 at 2:26 AM, <c.monty@xxxxxx> wrote:
> Hello!
>
> Based on the documentation for defining quotas in CephFS for any directory (http://docs.ceph.com/docs/master/cephfs/quota/), I defined a quota for attribute max_bytes:
> ld4257:~ # getfattr -n ceph.quota.max_bytes /mnt/ceph-fuse/MTY/
> getfattr: Removing leading '/' from absolute path names
> # file: mnt/ceph-fuse/MTY/
> ceph.quota.max_bytes="100000000"
>
> To validate if the quota is working, I write a 128MB file in /mnt/ceph-fuse/MTY:
> ld4257:~ # dd if=/dev/zero of=/mnt/ceph-fuse/MTY/128MBfile bs=64M count=2
> 2+0 records in
> 2+0 records out
> 134217728 bytes (134 MB, 128 MiB) copied, 0.351206 s, 382 MB/s
>
> This file is created correctly, and the utilization statistcs confirm it:
> ld4257:~ # rados df
> pool name KB objects clones degraded unfound rd rd KB wr wr KB
> hdb-backup 131072 32 0 0 0 8 8 43251 88572586
> hdb-backup_metadata 27920 27 0 0 0 301 168115 6459 55386
> rbd 0 0 0 0 0 0 0 0 0
> templates 0 0 0 0 0 0 0 0 0
> total used 9528188 59
> total avail 811829446772
> total space 811838974960
>
>
> Question:
> Why can I create a file with size 128MB after defining a quota of 100MB?
I don't have a cluster to check this on now but perhaps because a
sparse file (you wrote all zeros) does not consume its entire file
size in the quota (only what it uses). Retry with /dev/urandom.
(And the usual disclaimer: quotas only work with libcephfs/ceph-fuse.
The kernel client does not support quotas.)
Also, with older clients you needed to explicitly turn it on with the config option. I think that includes Jewel.
--
Patrick Donnelly
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
