From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kswapd continuously active
Date: Mon, 25 Jan 2010 14:06:27 +0100 [thread overview]
Message-ID: <20100125130627.GO13771@kernel.dk> (raw)
In-Reply-To: <alpine.LSU.2.01.1001230037350.20442@obet.zrqbmnf.qr>
On Sat, Jan 23 2010, Jan Engelhardt wrote:
> Hi,
>
>
> with 2.6.32.2 on sparc64 I am seeing that there is a sync(1) process
> busy in D state, with the following trace:
>
> sync D 000000000079299c 7552 4851 1 0x208061101000004
> Call Trace:
> [000000000053ca58] bdi_sched_wait+0xc/0x1c
> [000000000079299c] __wait_on_bit+0x58/0xb8
> [0000000000792a5c] out_of_line_wait_on_bit+0x60/0x74
> [000000000053ca3c] bdi_sync_writeback+0x6c/0x7c
> [000000000053ca78] sync_inodes_sb+0x10/0xfc
> [0000000000540dd0] __sync_filesystem+0x50/0x88
> [0000000000540ec8] sync_filesystems+0xc0/0x124
> [0000000000540f80] sys_sync+0x1c/0x48
> [0000000000406294] linux_sparc_syscall+0x34/0x44
>
> kswapd is also active all the time, writing something to disk - LED is
> blinking, and that's been going on for over half an hour despite the box
> being not busy. How do I see what kswapd is still flushing to disk? Even
> if all RAM (8 GB) was filled with dirty data, syncing it out would not
> take that long - that is to say, the sync process should have long
> exited.
That doesn't sound good. What does /proc/meminfo say? What file systems
are you using?
--
Jens Axboe
next prev parent reply other threads:[~2010-01-25 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 23:52 kswapd continuously active Jan Engelhardt
2010-01-25 13:06 ` Jens Axboe [this message]
2010-01-25 13:22 ` Jan Engelhardt
2010-02-05 12:35 ` Jan Engelhardt
2010-02-05 13:00 ` Jens Axboe
2010-02-05 13:09 ` Jan Engelhardt
2010-02-05 13:12 ` Jens Axboe
2010-02-05 13:24 ` Jan Engelhardt
2010-02-07 10:50 ` Jan Engelhardt
2010-02-08 0:07 ` Jan Engelhardt
2010-02-08 14:08 ` Jens Axboe
2010-02-10 15:18 ` Jan Engelhardt
2010-02-10 15:23 ` Jan Engelhardt
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=20100125130627.GO13771@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=jengelh@medozas.de \
--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