http://bugzilla.suse.com/show_bug.cgi?id=1131299 Bug ID: 1131299 Summary: fontconfig creates an enormous number of files in /var/cache/fontconfig that are never cleaned up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: shundhammer@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Earlier today I discovered that I had over 350,000 files in /var/cache/fontconfig that had accumulated in the 4 years that I have been using Tumbleweed. This not only consumed a lot of disk space, it also brought the system to a screeching halt every once in a while: All those files were in that single directory without any subdirectory. Even modern filesystems like XFS (which is what I use on that filesystem) break down completely in terms of performance when so many files are dumped into a single directory. It took more than 20 minutes (!) to remove the files (which needed "ls | xargs rm" because the argument list was much too long). So this directory needs to be cleaned up automatically every once in a while. Better yet, don't create so many files there in the first place. And even better, if so many files are needed, do it like the browsers (for their cache directories) and use an intermediate subdirectory (maybe on multiple levels) for better performance. [shundhammer @ morgul] ~ % cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190318" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190318" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190318" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" [shundhammer @ morgul] ~ % rpm -q fontconfig fontconfig-2.13.1-2.1.x86_64 After the cleanup, some files were recreated: [shundhammer @ morgul] ~ % ls -1 /var/cache/fontconfig 4bc6e738-4f14-4bb3-b1c1-113e1440c1c9-x86_64.cache-7 62a2cfd2-5b41-4739-9b75-5f646215de71-x86_64.cache-7 66f92a5c-8bae-4b9c-ba14-cf0cecec77a2-x86_64.cache-7 6f5661a4-b4de-4837-a6cb-77408b27d222-x86_64.cache-7 81ea5785-41f1-4169-a014-a9180af45296-x86_64.cache-7 8bfbb25c-ea26-45ef-9fa8-8bc1cd23e6c8-x86_64.cache-7 a74dc887-85ed-4c63-a0b3-3520f4be1244-x86_64.cache-7 b77b3349-5612-4eeb-95e2-a017bef0b7b7-x86_64.cache-7 be89a7c6-246d-476f-9e7e-e63a135fcfea-x86_64.cache-7 c210a518-33c5-48da-a1b9-55b4a4895c28-x86_64.cache-7 cbe681e7-c178-45ed-a1dd-523a6515af68-x86_64.cache-7 e0f28a10-064e-443c-9da1-1ad111a20ab1-x86_64.cache-7 e50cc437-bedf-4c0d-a1fb-f06def71d136-x86_64.cache-7 f5d4db0f-7acc-412e-b184-266c457f1a79-x86_64.cache-7 f6c4cbb4-f12c-4f74-8d69-264c5d8bbf56-x86_64.cache-7 That is a reasonable number. 350,000+ is not. -- You are receiving this mail because: You are on the CC list for the bug.