Bug 1000699
Summary: | Nightmare of updates | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||||
Component: | selinux-policy-targeted | Assignee: | Miroslav Grepl <mgrepl> | ||||||||||||
Status: | CLOSED EOL | QA Contact: | Ben Levenson <benl> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 19 | CC: | dwalsh | ||||||||||||
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: | 2015-02-17 16:54:13 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: | |||||||||||||||
Attachments: |
|
Description
Mikhail
2013-08-24 11:49:02 UTC
Created attachment 789854 [details]
screenshot of htop
How many files to you have in those directories? [mikhail@localhost ~]$ find /home/mikhail/.cache /home/mikhail-old/.cache /home/mikhail/.config /home/mikhail-old/.config -type f|wc -l 3209162 Any chance to clean up these directories? This not solving problem because they grow again. Mikhail and if you run restorecon -R -v /home/mikhail/.cache /home/mikhail-old/.cache /home/mikhail/.config /home/mikhail-old/.config Takes hours? # time restorecon -R -v /home/mikhail/.cache /home/mikhail-old/.cache /home/mikhail/.config /home/mikhail-old/.config restorecon get context on /home/mikhail/.cache/google-chrome/Default/Cache/f32e5ad3f7718b0a_2 failed: 'No such file or directory' restorecon: Warning no default label for /home/mikhail-old/.cache/deadbeef/covers/Ñåðãåé Ìèíàåâ Сергей Минаев real 220m36.509s user 0m43.331s sys 1m10.609s But why are they so huge? find ~/.config | wc -l 1855 find ~/.cache | wc -l 6042 And I have never cleaned these out? [mikhail@localhost ~]$ find ~/.config | wc -l 8792 [mikhail@localhost ~]$ find ~/.cache | wc -l 3166828 Created attachment 791977 [details]
screenshot mc1
Created attachment 791978 [details]
screenshot mc2
Created attachment 791980 [details]
screenshot mc3
If chrome is throwing hundreds of thousands of files into you homedir, think you have a bug with them. I would remove some of those cache files https://support.google.com/chrome/answer/95582?hl=en This is the first bug we have seen complaining about this. But I think we should remove this code if google is dropping thousands of files into these directrories. The reason we are doing it is if new directory labeling is added to .config or .cache subdirs, we want to make sure they are labeled correctly. I removed the directory ~/.cache/google-chrome all night. And while deleting I can not do anything, all wildly lag. This is kernel problem or ext4? But that's not all. For two days in the directory ~/.cache/google-chrome/Default/Cache has created 199184 files. And the growth rate is not reduced. Midnight Commander enter in this folder more than a minute. :( Created attachment 792663 [details]
screenshot mc after two days of removing .cache directory
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |