Bug 64152
Summary: | ext3 file system reset causes loss of all but 4 meg available memory | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Steve Wells <swells> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-27 19:59:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Steve Wells
2002-04-26 17:26:02 UTC
What is a "file reset operation"? I assume you mean a "fsck" filesystem check. Yes, that will use all the memory in the system for caching. No, that memory will not be returned once fsck completes --- the whole point of a cache is that until we need to use that memory for something else, we might as well keep the contents of the cache around just in case they turn out to be useful. The memory that is in use should be returned as soon as anything else in the system needs it. Seeing no free memory in top just indicates that the cache is performing as designed. Presumption that memory is being returned by cache once other apps need is incorrect; in this case we are running Java VM and (according to Top) is then loaded using considerable OS swap system space, rather than physical memory, which it will when loaded without having previously run fsck. Process memory which was swapped out during the fsck run may quite legitimately remain on swap afterwards if nothing needs it paged back into memory. If the swapped memory _is_ needed, but is only touched for read access, then the copy in the swap area on disk remains valid and is not removed. There are all sorts of reasons why swap may remain in use afterwards. If you see excessive swap activity take place for a prolonged period after the fsck, then that might be a performance problem. The mere presence of a certain amount of swapped page in "free" output is not a problem. |