From: Roland Eggner <edvx1@systemanalysen.net>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused
Date: Sun, 25 Nov 2012 23:59:55 +0100 [thread overview]
Message-ID: <20121125225954.GA14653@mobil.systemanalysen.net> (raw)
In-Reply-To: <1353871800.22969.28.camel@soupermouf>
[-- Attachment #1: Type: text/plain, Size: 2178 bytes --]
On 2012-11-25 Sunday at 21:30 +0200 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!
Hello Dimitrios,
I would try a 2.6.27.* kernel, for following reasons:
(1) Kernel development since 2.6.27 achieved significant performance
improvements at the cost of exploding memory consumption by the kernel for
_internal_ data structures. I am currently using a 3.2.34 kernel on a Notebook
with 4 G RAM. 0,5 … 1 G RAM is usually occupied just by kernel slab [1]; this
memory cannot be swapped, it cannot be released by other means than rebooting,
and there seems to be _no_ adjustment to memory pressure. I am surprised,
that you have managed to boot a 3.6.* kernel at all with only 128 M RAM.
(2) At the time, when I used a PIII-Notebook, kernels 2.6.27 to 2.6.29 where
current. Thus chances are good, that a 2.6.27.* kernel will support chipset,
PCI bus and devices of your notebook. 2.6.27 got longterm maintainance, the
latest release in the linux-stable git repository is 2.6.27.62.
So Q @ LKML community:
Does anybody know a x86 distribution or live-CD using a 2.6.27.* kernel?
[1] Picture described in my LKML message
Date: Fri, 20 Jan 2012 01:08:00 +0100
Subject: Re: [kmemleak report 1/2] kernel 3.1.6, x86_64: mm, xfs ?, vfs ?
remained the same with _every_ 3.1.* and 3.2.* kernel tried so far.
--
Roland
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-11-25 22:59 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 ` 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 ` Roland Eggner [this message]
2012-11-25 23:56 ` backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused 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
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=20121125225954.GA14653@mobil.systemanalysen.net \
--to=edvx1@systemanalysen.net \
--cc=jimis@gmx.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®