All of lore.kernel.org
 help / color / mirror / Atom feed
From: jay.aurabind@gmail.com (Jay Aurabind)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kworker and jbd2 constantly writing to hdd
Date: Fri, 25 Apr 2014 12:22:55 +0530	[thread overview]
Message-ID: <535A0647.1090601@gmail.com> (raw)

Hi,

My kernel is 3.13.0-24, ubuntu 14.04. I have an ext4 root partition, and
I can see 2 threads (kworker,jbd2) periodically writing to hdd at about
roughly (1,5) second interval.

I disabled journalling so that jbd2 is gone. Still, the kworker thread
is bugging me. Is it really necessary for the system to work properly?

cat /proc/<PID>/stack of the kworker is:

[<ffffffff810846f1>] worker_thread+0x1d1/0x410
[<ffffffff8108b312>] kthread+0xd2/0xf0
[<ffffffff8172637c>] ret_from_fork+0x7c/0xb0
[<ffffffffffffffff>] 0xffffffffffffffff

It doesnt make any sense to me.

On tracing this kworker, I found this line:

kworker/u8:1-68    [000] d...  1135.724955: workqueue_queue_work: \
work struct=ffff8800701e00b8 function= \
ata_sff_pio_task workqueue=ffff880073e6f600 req_cpu=256 cpu=0


So it seems the function ata_sff_pio_task in
drivers/ata/libata-sff.c#L1343 is being run. Why is it getting called
periodically? Is it possible to suppress it ?

Someone else has also posted about it in arch linux forum:
https://bbs.archlinux.org/viewtopic.php?id=178632, smelling a kernel
bug. But I dont feel it could be a bug, because some other kernel thread
must be requesting some operation, which could be the reason for a
"generic" ata code to pop up.

I'm concerned because my harddisk heats up unnecessarily (though not
violently), and I never had such a situation while using windows (couple
of years ago). I am a noob when it comes to kernel programming, (just
started ldd3), so please correct me if I'm wrong. Please also suggest
something to fix this issue, or to investigate more into this.


Thanks and Regards,
Jay

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140425/7124c090/attachment.bin 

             reply	other threads:[~2014-04-25  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  6:52 Jay Aurabind [this message]
2014-04-25 12:18 ` Kworker and jbd2 constantly writing to hdd Mulyadi Santosa
2014-04-25 14:11   ` Jay Aurabind

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=535A0647.1090601@gmail.com \
    --to=jay.aurabind@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.