Ceph » CephFS

For this test I was using the below versions:

ceph version 10.2.1 (3a66dd4f30852819c1bdaa8ec23c795d4ad77269)
nfs-ganesha Starting: Version 2.1.1-pre

I have set a quota on /liam/ as shown below:

root@ceph-ganesha-1:/nfs# getfattr -n ceph.quota.max_bytes liam

1. file: liam
   ceph.quota.max_bytes="100000000"

root@ceph-ganesha-1:/nfs# mount | grep nfs
ceph-fuse on /nfs type fuse.ceph-fuse (rw,nosuid,nodev,allow_other,default_permissions)

I have used cephfuse here just for the purpose of setting the ceph.quota.max_byte attribute.

I then use the below 'ganesha.conf' config to export this folder to a remote nfs client:

'EXPORT {
Export_ID = 1;
Path = "/liam";
Pseudo = "/liam";
NFS_Protocols = "4";
Transport_Protocols = TCP;
SecType = "sys";

FSAL {
        Name = CEPH;
    }

CLIENT {
        Clients =  x.x.x.x;
        Access_Type = RW;
        Squash = None;
    }

}
'
The export works as expected, But the quota is never enforced, I can keep on writing new files taking up 100's GB of disk space.

As the Ceph client library is responsible for enforcing quotas maybe this is missing from the ganesha FSAL, even with debug logging enabled I don't see any reference to quotas at all.

In a Ganesha (V2.5-dev-6) and Ceph (latest Jewel) setup, I set `client quota = true` in the client section of the ceph.conf (as suggested by Greg) used by Ganesha, and could see that quotas were enforced on the NFS share. Maybe this issue can be closed?

The client_quota option is enabled by default in Kraken (https://github.com/ceph/ceph/commit/48acd4b35c860589d43e7cce7a80b5a023fd9f21).