From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: util-linux-owner@vger.kernel.org Received: from plane.gmane.org ([80.91.229.3]:36497 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754659AbbLDHtq (ORCPT ); Fri, 4 Dec 2015 02:49:46 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1a4l7g-0006r1-6f for util-linux@vger.kernel.org; Fri, 04 Dec 2015 08:49:44 +0100 Received: from ip4d14b373.dynamic.kabel-deutschland.de ([77.20.179.115]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Dec 2015 08:49:44 +0100 Received: from for-gmane by ip4d14b373.dynamic.kabel-deutschland.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Dec 2015 08:49:44 +0100 To: util-linux@vger.kernel.org From: "U.Mutlu" Subject: Re: fsck memory leak Date: Fri, 4 Dec 2015 08:49:34 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed In-Reply-To: Sender: util-linux-owner@vger.kernel.org List-ID: 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