Bug 902483
| Summary: | Cannot handle 2000 mounts | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ben Greear <greearb> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | david, joeym, johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-04 22:33:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ben Greear
2013-01-21 18:56:13 UTC
Have you increased the default file descriptor limit in units/system.conf to handle all these mount points? Also see... http://en.usenet.digipedia.org/thread/18978/19676/ This may be fixed by:
commit 4096d6f5879aef73e20dd7b62a01f447629945b0
Author: Lennart Poettering <lennart>
Date: Mon Sep 17 16:35:59 2012 +0200
main: bump up RLIMIT_NOFILE for systemd itself
... which is not in F17 however.
I tried editing file: /etc/systemd/system.conf and changed the setting as below: DefaultLimitNOFILE=6000 It still complained and hung on reboot when I have 3000 mounts. I have updated it to 12,000 and will try again. But, maybe the systemd code needs some better logic to deal with lots of open files and/or better recovery logic if it does hit an error? Even if it can't bring things down gracefully, it would be nice if at least it could manage a reboot... DefaultLimitNOFILE has no effect on systemd itself. It's a setting for the services it spawns. We really need to backport that patch. We can also consider economizing systemd's fd usage. For example, timerfds - we could have a tree of timeouts and schedule always only the earliest one using a single timerfd. That patch in comment #2 still hard-codes things (though 64k is big enough for anyone! (tm)) Maybe instead make it configurable in the system.conf file, with a 64k default? If someone can cook up a patched RPM for 64-bit Fedora 17, I'll be happy to test it. *** Bug 908531 has been marked as a duplicate of this bug. *** We would love to see this backported to F17 which was our reason for opening the dupe bug 908531 (it was more of a request than a bug report.) Ben, we have backported this to f17 rpms because it is very important to us. You can build rpm's yourself from this repo: https://github.com/pantheon-systems/systemd sudo yum install -y yum-utils rpm-build spectool sudo yum-builddep systemd git clone git:pantheon-systems/systemd.git cd systemd/ git checkout f17 cd .. mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} spectool --get-files --sourcedir systemd/systemd.spec cp systemd/* ~/rpmbuild/SOURCES/ rpmbuild -ba systemd/systemd.spec systemd-44-24.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/systemd-44-24.fc17 Package systemd-44-24.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-44-24.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2564/systemd-44-24.fc17 then log in and leave karma (feedback). systemd-44-24.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |