Bug 905635
| Summary: | mysql and tmp on tmpfs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Henrique Martins <fedora> | ||||
| Component: | mysql | Assignee: | Honza Horak <hhorak> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | hhorak, tgl | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | community-mysql-5.5.31-7.fc19 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 962087 (view as bug list) | Environment: | |||||
| Last Closed: | 2013-06-13 06:52:55 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 962087 | ||||||
| Attachments: |
|
||||||
|
Description
Henrique Martins
2013-01-29 19:57:32 UTC
TBH, fixing this in mysql is the Wrong Thing. F18's choice to put /tmp on tmpfs by default is questionable even on personal/laptop systems, and utterly brain-dead for servers. I'd recommend turning it off system-wide rather than hacking applications one at a time. See https://fedoraproject.org/wiki/Features/tmp-on-tmpfs Understood, and I actually already disabled this to take effect as of the next reboot of the machine where I had this problem. However, as far as I can find with google, it seems that Fedora/FESCO is going to keep this going forward, so someone needs to file bug reports for every single application, for the benefit of people that won't turn it off. According to [1] having TMPDIR on tmpfs can cause even bigger troubles in mysql in case of replication slave. If we won't concern a possibility of reverting that F18 feature (I don't believe that happens), I'd vote to change mysql's default to /var/tmp. Then in case somebody believes /tmp will mean a performance improvement for him and limited space wouldn't be an issue, one can always define tmpdir variable in the my.cnf file. For most of cases /var/tmp should be good enough. [1] http://dev.mysql.com/doc/refman/5.5/en/server-options.html#option_mysqld_tmpdir Created attachment 696099 [details] Make tmpdir a configurable option I've sent the attached patch to MySQL and MariaDB upstreams. It adds ability to specify tmpdir using "-DTMPDIR=/var/tmp" during build configuration. http://bugs.mysql.com/bug.php?id=68338 https://mariadb.atlassian.net/browse/MDEV-4165 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. community-mysql-5.5.31-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/community-mysql-5.5.31-7.fc19 Package community-mysql-5.5.31-7.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing community-mysql-5.5.31-7.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10020/community-mysql-5.5.31-7.fc19 then log in and leave karma (feedback). community-mysql-5.5.31-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |