Description of problem: quota is not turned on after boot. Looks like quotaon.service is broken. Version-Release number of selected component (if applicable): systemd-37-3.fc16.x86_64 systemd-units-37-3.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. configure quota 2. reboot system 3. quotaon -ap # print status Actual results: group quota on / (/dev/vda2) is off user quota on / (/dev/vda2) is off Expected results: group quota on / (/dev/vda2) is on user quota on / (/dev/vda2) is on Additional info: Looks like quotaon.service is broken. First problem is, that there is no Install/WantedBy section: [root@server ~]# systemctl enable quotaon.service Warning: unit files do not carry install information. No operation executed. Adding this: [Install] WantedBy=local-fs.target After adding Install section there is another problem, that this script is trying to run before filesystem is mounted read-write. Adding "remount-rootfs.service" helps for me. Please, consider making other changes too: - check if if will run after other filesystems are ready - check if it's enabled by default - check quotacheck.service file too
quotacheck.service and quotaon.service are supposed to be pulled automatically by mount units that are configured with "usrquota" "grpquota", "quota", "usrjquota" or "grpjquota" mount options. What's in your /etc/fstab?
for example: LABEL=/home /home ext3 nosuid,usrquota,grpquota 1 2 I have three systems, two of them installed as Fedora 16, one upgraded from Fedora 14 (where quota worked). Looks like it's ignored on all systems.
Looks like quotaon.service is run automatically, but fails (selinux is in permissive mode): [ 5.945996] systemd[1]: quotaon.service: main process exited, code=exited, status=1 Starting Enable File System Quotas failed, see 'systemctl status quotaon.service ' for details. [ 5.960802] systemd[1]: Unit quotaon.service entered failed state. [ 5.974954] quotaon[372]: quotaon: using //aquota.user on /dev/vda2 [/]: Súborový systém dovoľuje len čítanie [ 6.066132] EXT4-fs (vda2): re-mounted. Opts: usrquota Started Remount Root FS. Starting Configure read-only root support... This testing system has quotas on root (/) filesystem. May be you should add remount-rootfs.service to After section. Another problem should be if I have multiple filesystems with quota. Is quotaon -a started after mount of each? If yes, quotaon fails on >=2nd filesystem. Another test, with 2 filesystems (/ a /home), then quota on / is turned on: group quota on / (/dev/vda2) is off user quota on / (/dev/vda2) is on group quota on /home (/dev/vda4) is off user quota on /home (/dev/vda4) is off
Fixed upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=9ddc4a26e56b06cd7774a03597980351855d8d54
(In reply to comment #4) > Fixed upstream: > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=9ddc4a26e56b06cd7774a03597980351855d8d54 This link displays only: "No repositories found", so I can't check. Please can you also build at least an koji build?
The cgit viewer may have had an outage. The link works for me now. A scratch build. Here you are: http://koji.fedoraproject.org/koji/taskinfo?taskID=3684294
Looks good for me on my testing system. Can you build an testing update? Then I can more tests on my production systems.
systemd-37-7.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16
Package systemd-37-7.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-7.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16 then log in and leave karma (feedback).
(In reply to comment #8) > systemd-37-7.fc16 has been submitted as an update for Fedora 16. > https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16 This update does not work for me. Even if quota may be started, some other services are not started, for example spamd. Sometimes start, but later stop. May be there are some problems with spamd.pid file, which will not be created. I have no more time to test on this production system. I will try to do more tests on my testing system tomorrow.
Package systemd-37-8.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-8.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-8.fc16 then log in and leave karma (feedback).
(In reply to comment #10) > This update does not work for me. Even if quota may be started, some other > services are not started, for example spamd. Sometimes start, but later stop. > May be there are some problems with spamd.pid file, which will not be created. > I have no more time to test on this production system. I will try to do more > tests on my testing system tomorrow. When you get to it, please file a new bug and attach the debug log obtained by booting with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg" and saving the output of the dmesg command.
(In reply to comment #10) > May be there are some problems with spamd.pid file, which will not be created. Right, it's a bug in the spamassassin.service unit file. bug 783108. (In reply to comment #12) > When you get to it, please file a new bug and attach the debug log No need for that anymore.
Package systemd-37-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16 then log in and leave karma (feedback).
Can you fix this bug for Fedora 15 too?
Package systemd-37-11.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-11.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-11.fc16 then log in and leave karma (feedback).
systemd-37-11.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
systemd-26-15.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/systemd-26-15.fc15
(In reply to comment #15) > Can you fix this bug for Fedora 15 too? Let me know in https://admin.fedoraproject.org/updates/FEDORA-2012-1068 if the update fixes the bug on F15.
> Let me know in https://admin.fedoraproject.org/updates/FEDORA-2012-1068 if the > update fixes the bug on F15. Yes, quota is on on F15 too. No other side effects yet.
systemd-26-16.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.