From: Dimitrios Apostolou <jimis@gmx.net>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Roland Eggner <edvx1@systemanalysen.net>,
Catalin Marinas <catalin.marinas@arm.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused
Date: Fri, 7 Dec 2012 17:26:27 +0200 (EET) [thread overview]
Message-ID: <alpine.LFD.2.02.1212071720590.1646@soupermouf> (raw)
In-Reply-To: <20121206164312.GB21029@quack.suse.cz>
Hi Jan, thanks for your help, with this commit I can't reproduce the
problem. The problematic workload is no more inflating the
ext4_inode_cache, in fact I've been able to run even heavier workloads
with the ext4_inode_cache never surpassing 2-4MB.
Thanks everyone for helping,
Dimitris
On Thu, 6 Dec 2012, Jan Kara wrote:
> On Thu 06-12-12 17:15:37, Dimitrios Apostolou wrote:
>> On Thu, 6 Dec 2012, Jan Kara wrote:
>>> On Sun 25-11-12 21:30:00, Dimitrios Apostolou wrote:
>>>> On Sun, 2012-11-25 at 15:55 +0200, Dimitrios Apostolou wrote:
>>>>> on an old PIII-500MHz laptop, 128MB RAM, kernel 3.6.6, I started a
>>>>> backup process (tar|xz -4, nice'd and ionice'd -c3) from ext4 on local
>>>>> ATA disk to ext3 on external USB disk (USB-2.0 port on PCMCIA card).
>>>>> Even though earlier system load was minimal, free memory was plenty, the
>>>>> system now is unresponsive and is thrashing the disk, but the swapfile
>>>>> is rarely touched.
>>>>
>>>> I'm now having the same experience even though I replaced xz (which
>>>> needed ~50MB RAM) with gzip. Even though I feel the realtime root shell
>>>> is a bit more responsive than before, the OOM killer is out killing
>>>> small processes like syslog-ng and systemd-logind... The
>>>> ext4_inode_cache slab is taking almost all my memory (117MB). Please
>>>> advise!
>>> Hmm, it seems commit 4eff96dd5283a102e0c1cac95247090be74a38ed might be
>>> interesting for you. It landed in -stable kernels recently as well if I
>>> remember right...
>>
>> Thanks, I appreciate your help as I'm stuck in a dead end now, and
>> I've been trying to write some debug hook that prints all
>> ext4_inodes and the reason they are pinned (is there an easy way to
>> find this out?).
>>
>> So maybe there is a typo in the SHA1 sum you provided? Gitweb can't
>> find it in Linus' tree.
> Strange. You are right gitweb doesn't show the SHA1 but I can see it in
> my git repo I pulled from Linus. Anyway, I've attached the fix for your
> convenience.
>
> Honza
>
> --
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
>
next prev parent reply other threads:[~2012-12-07 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353851735.22969.18.camel@soupermouf>
2012-11-25 19:30 ` backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused Dimitrios Apostolou
2012-11-25 22:41 ` kmemleak failure (was Re: backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused) Dimitrios Apostolou
2012-11-25 23:19 ` Dimitrios Apostolou
2012-11-25 22:59 ` backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused Roland Eggner
2012-11-25 23:56 ` Alan Cox
2012-11-26 3:11 ` Roland Eggner
2012-12-06 14:20 ` Jan Kara
2012-12-06 15:15 ` Dimitrios Apostolou
2012-12-06 16:43 ` Jan Kara
2012-12-07 15:26 ` Dimitrios Apostolou [this message]
2012-11-25 15:03 Dimitrios Apostolou
2012-12-02 12:44 ` Dimitrios Apostolou
2012-12-02 22:50 ` Roland Eggner
2012-12-02 23:56 ` Dimitrios Apostolou
2012-12-03 17:43 ` Theodore Ts'o
2012-12-03 18:47 ` Eric Paris
2012-12-03 19:35 ` Dimitrios Apostolou
2012-12-03 20:00 ` Dimitrios Apostolou
2012-12-03 18:03 ` Roland Eggner
2012-12-03 19:25 ` Dimitrios Apostolou
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=alpine.LFD.2.02.1212071720590.1646@soupermouf \
--to=jimis@gmx.net \
--cc=catalin.marinas@arm.com \
--cc=edvx1@systemanalysen.net \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).