Hi Oliver, We saw the same issue after upgrading to mimic. IIRC we could make the max_bytes xattr visible by touching an empty file in the dir (thereby updating the dir inode). e.g. touch /cephfs/user/freyermu/.quota; rm /cephfs/user/freyermu/.quota Does that work? -- dan On Mon, May 27, 2019 at 11:36 AM Oliver Freyermuth <freyermuth@xxxxxxxxxxxxxxxxxx> wrote: > > Dear Cephalopodians, > > in the process of migrating a cluster from Luminous (12.2.12) to Mimic (13.2.5), we have upgraded the FUSE clients first (we took the chance during a time of low activity), > thinking that this should not cause any issues. All MDS+MON+OSDs are still on Luminous, 12.2.12. > > However, it seems quotas have stopped working - with a (FUSE) Mimic client (13.2.5), I see: > $ getfattr --absolute-names --only-values -n ceph.quota.max_bytes /cephfs/user/freyermu/ > /cephfs/user/freyermu/: ceph.quota.max_bytes: No such attribute > > A Luminous client (12.2.12) on the same cluster sees: > $ getfattr --absolute-names --only-values -n ceph.quota.max_bytes /cephfs/user/freyermu/ > 5000000000000 > > It does not seem as if the attribute has been renamed (e.g. https://github.com/ceph/ceph/blob/mimic/qa/tasks/cephfs/test_quota.py still references it, same for the docs), > and I have to assume the clients also do not enforce quota if they do not see it. > > Is this a known incompatibility between Mimic clients and a Luminous cluster? > The release notes of Mimic only mention that quota support was added to the kernel client, but nothing else quota related catches my eye. > > Cheers, > Oliver > > _______________________________________________ > 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
 |