From: Dimitrios Apostolou <jimis@gmx.net>
To: Eric Paris <eparis@parisplace.org>, "Theodore Ts'o" <tytso@mit.edu>
Cc: Roland Eggner <edvx1@systemanalysen.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused
Date: Mon, 3 Dec 2012 22:00:06 +0200 (EET) [thread overview]
Message-ID: <alpine.LFD.2.02.1212032157480.4173@soupermouf> (raw)
In-Reply-To: <alpine.LFD.2.02.1212032125520.4173@soupermouf>
On Mon, 3 Dec 2012, Dimitrios Apostolou wrote:
>
> I've managed to reproduce the scenario with concurrent "du" commands running
> on the filesystems. I'll try doing it once more, but it may take a while to
> get the dmesg/slabinfo etc output, since even a realtime root shell is
> non-responsive for many minutes.
>
> What other debug output do you suggest to get, to find out why ext4 inodes
> are pinned?
Important detail: one of the filesystems contains *huge* maildirs,
containing hundreds of thousands of messages.
Dimitris
next prev parent reply other threads:[~2012-12-03 20:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 15:03 backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused 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 [this message]
2012-12-03 18:03 ` Roland Eggner
2012-12-03 19:25 ` Dimitrios Apostolou
[not found] <1353851735.22969.18.camel@soupermouf>
2012-11-25 19:30 ` Dimitrios Apostolou
2012-11-25 22:59 ` 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
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.1212032157480.4173@soupermouf \
--to=jimis@gmx.net \
--cc=catalin.marinas@arm.com \
--cc=edvx1@systemanalysen.net \
--cc=eparis@parisplace.org \
--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