Hi I have similar problems. Somehow the filesystem quota gets enabled before the quota.service target is run.
journalctl gives: Oct 05 17:47:37 fs-bm-1 systemd[1]: quota.service: main process exited, code=exited, status=1/FAILURE Oct 05 17:47:37 fs-bm-1 systemd[1]: Failed to start Check And Enable File System Quotas. Oct 05 17:47:37 fs-bm-1 systemd[1]: Unit quota.service entered failed state. To check this I introduced "quotaon -ap" into/usr/share/quota/quotaon.sh on line 48 (before "LC_MESSAGES=C $on -ap|grep -q "is off" || exit 0"). After introducing the line the journal reads like this Oct 05 17:50:40 fs-bm-1 quotaon.sh[278]: group quota on /srv/nfs4/users (/dev/mapper/fs--ng--1_vg1-home_lv) is off Oct 05 17:50:40 fs-bm-1 quotaon.sh[278]: user quota on /srv/nfs4/users (/dev/mapper/fs--ng--1_vg1-home_lv) is on Oct 05 17:50:40 fs-bm-1 systemd[1]: quota.service: main process exited, code=exited, status=1/FAILURE Oct 05 17:50:40 fs-bm-1 systemd[1]: Failed to start Check And Enable File System Quotas. Oct 05 17:50:40 fs-bm-1 systemd[1]: Unit quota.service entered failed state. Because group quota is off quotaon.sh continues but since the userquota is already set on the final "quotaon -aug" fails. quotaon -aug quotaon: using /srv/nfs4/users/aquota.user on /dev/mapper/fs--ng--1_vg1-home_lv [/srv/nfs4/users]: Device or resource busy If the quotas needs to be checked this may fail for the same reasons. I am not shure, but this may also lead to wrong quota informations after file system crashes? Thanks Hendrik Naumann PS. fstab reads: UUID="bc0d7c7e-2b6b-4010-b5e5-36bc94c21443" /srv/nfs4/users ext4 defaults,acl,quota 0 2 /srv/nfs4/users /home/users none defaults,bind 0 0
