From: Marcus Sundman <marcus@hibox.fi>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Debugging system freezes on filesystem writes
Date: Fri, 09 Nov 2012 15:12:43 +0200 [thread overview]
Message-ID: <509D014B.2080709@hibox.fi> (raw)
In-Reply-To: <509C4339.2090506@hibox.fi>
On 09.11.2012 01:41, Marcus Sundman wrote:
> On 07.11.2012 18:17, Jan Kara wrote:
>> On Fri 02-11-12 04:19:24, Marcus Sundman wrote:
>>> Also, and this might be important, according to iotop there is
>>> almost no disk writing going on during the freeze. (Occasionally
>>> there are a few MB/s, but mostly it's 0-200 kB/s.) Well, at least
>>> when an iotop running on nice -20 hasn't frozen completely, which it
>>> does during the more severe freezes.
>> OK, it seems as if your machine has some problems with memory
>> allocations. Can you capture /proc/vmstat before the freeze and after
>> the
>> freeze and send them for comparison. Maybe it will show us what is the
>> system doing.
>
> t=01:06 http://sundman.iki.fi/vmstat.pre-freeze.txt
> t=01:08 http://sundman.iki.fi/vmstat.during-freeze.txt
> t=01:12 http://sundman.iki.fi/vmstat.post-freeze.txt
Here are some more vmstats:
http://sundman.iki.fi/vmstats.tar.gz
They are from running this:
while true; do cat /proc/vmstat > "vmstat.$(date +%FT%X).txt"; sleep 10;
done
There were lots and lots of freezes for almost 20 mins from 14:37:45
onwards, pretty much constantly, but at 14:56:50 the freezes suddenly
stopped and everything went back to how it should be.
Thanks,
Marcus
next prev parent reply other threads:[~2012-11-09 13:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:39 Debugging system freezes on filesystem writes Marcus Sundman
2012-11-01 19:01 ` Jan Kara
2012-11-02 2:19 ` Marcus Sundman
2012-11-07 16:17 ` Jan Kara
2012-11-08 23:41 ` Marcus Sundman
2012-11-09 13:12 ` Marcus Sundman [this message]
2012-11-13 13:51 ` Jan Kara
2012-11-16 1:11 ` Marcus Sundman
2012-11-21 23:30 ` Jan Kara
2012-11-27 16:14 ` Marcus Sundman
2012-12-05 15:32 ` Jan Kara
2013-02-20 8:42 ` Marcus Sundman
2013-02-20 11:40 ` Marcus Sundman
2013-02-22 20:51 ` Jan Kara
2013-02-22 23:27 ` Marcus Sundman
2013-02-24 0:12 ` Dave Chinner
2013-02-24 1:20 ` Theodore Ts'o
2013-02-26 18:41 ` Marcus Sundman
2013-02-26 22:17 ` Theodore Ts'o
2013-02-26 23:17 ` Jan Kara
2013-09-12 12:57 ` Marcus Sundman
2013-09-12 13:10 ` Jan Kara
2013-09-12 13:47 ` Marcus Sundman
2013-09-12 14:39 ` Jan Kara
2013-09-12 15:08 ` Marcus Sundman
2013-09-12 16:35 ` Jan Kara
2013-09-12 17:59 ` Marcus Sundman
2013-09-12 20:46 ` Jan Kara
2013-09-13 6:35 ` Marcus Sundman
2013-09-13 20:54 ` Jan Kara
2013-09-14 2:41 ` Theodore Ts'o
2013-09-15 19:19 ` Marcus Sundman
2013-09-16 0:06 ` Theodore Ts'o
2013-02-25 13:05 ` Jan Kara
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=509D014B.2080709@hibox.fi \
--to=marcus@hibox.fi \
--cc=jack@suse.cz \
--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 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.