From: "U.Mutlu" <for-gmane@mutluit.com>
To: util-linux@vger.kernel.org
Subject: Re: fsck memory leak
Date: Fri, 4 Dec 2015 08:49:34 +0100 [thread overview]
Message-ID: <n3rgif$72q$1@ger.gmane.org> (raw)
In-Reply-To: <n3rei3$8l3$1@ger.gmane.org>
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
next prev parent reply other threads:[~2015-12-04 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 7:15 fsck memory leak U.Mutlu
2015-12-04 7:49 ` U.Mutlu [this message]
2015-12-04 10:21 ` Karel Zak
2015-12-04 18:00 ` U.Mutlu
2015-12-04 15:19 ` Theodore Ts'o
2015-12-04 17:53 ` U.Mutlu
2015-12-04 19:09 ` U.Mutlu
2015-12-04 19:58 ` Theodore Ts'o
2015-12-04 20:31 ` U.Mutlu
2015-12-04 21:40 ` Ruediger Meier
2015-12-04 22:26 ` U.Mutlu
2015-12-04 22:03 ` Mike Frysinger
2015-12-04 22:17 ` Theodore Ts'o
2015-12-04 22:01 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2015-12-04 23:08 Dave Rutherford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='n3rgif$72q$1@ger.gmane.org' \
--to=for-gmane@mutluit.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.