Re: fsck memory leak

["U.Mutlu" <for-gmane@mutluit.com>]

Karel Zak wrote on 12/04/2015 11:21 AM:
> On Fri, Dec 04, 2015 at 08:49:34AM +0100, U.Mutlu wrote:
>> U.Mutlu wrote on 12/04/2015 08:15 AM:
>>> Hi,
>>> when I as root do "touch /forcefsck" and reboot, then fsck will be done.
>>> But afterwards one has less free memory available than normal.
>>> Example:
>>> used mem immediately after login:
>>>   without fsck during boot:  98 MB (this the normal level here)
>>>   with fsck during boot   : 139 MB
>>> So, there is a memory leak of about 41 MB.
>>
>> This discrepancy is reproducible here, ie. happens always.
>>
>> Not sure, but it could also be a kernel issue, because
>> the longer the system runs the more memory gets bound.
>> The source of the culprit is not easily detectable.
>> I guess it gets eaten by the kernel, probably by the ext4-driver.
>>
>>> fsck from util-linux 2.25.2
>>> Filesys: ext4, 500 MB SSD
>>
>> fix: of course 500 GB was meant
>>
>>> OS: Debian 8 X86_64, uptodate
>
> And are you talking about fsck (wrapper) or fsck.ext4 (from
> e2fsprogs)?

I don't know which one gets used in the above scenario because
it is done automatically by the system.

But the problem is solved now by setting /proc/sys/vm/drop_caches
to the value 3 as was written in the other postings.

>
>      Karel