From: James Cloos <cloos@jhcloos.com>
To: Chris Mason <clm@fb.com>
Cc: Tsutomu Itoh <t-itoh@jp.fujitsu.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [3.16-rc1] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u25:4:5189]
Date: Wed, 09 Jul 2014 13:14:53 -0400 [thread overview]
Message-ID: <m3egxu314i.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <539FC896.5010909@fb.com> (Chris Mason's message of "Tue, 17 Jun 2014 00:48:22 -0400")
It looks like I just hit this on rc4. (I compiled the earlier rc
versions, but hadn't rebooted until yesterday.)
I don't think I see anything in the git log since rc1 which is relevant,
but just in case one of those tried to fix this, its still there.
The stuck processes are:
]btrfs-transacti] btrfs_wait_and_free_delalloc_work
rsync writeback_inodes_sb_nr
rsync reserve_metadata_bytes
git-merge sleep_on_page_killable
/bin/sync sync_inodes_sb
(The two rsync processes are separate; each to its one directory.)
The fs with those processes is mounted with noatime,compress.
Interestingly, I also use btrfs /var/log, also with noatime,compress,
but that one is fine.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2014-07-09 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 6:35 [3.16-rc1] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u25:4:5189] Tsutomu Itoh
2014-06-16 17:56 ` Chris Mason
2014-06-16 23:28 ` Tsutomu Itoh
2014-06-16 23:52 ` Chris Mason
2014-06-16 23:57 ` Tsutomu Itoh
2014-06-17 0:47 ` Chris Mason
2014-06-17 2:10 ` Tsutomu Itoh
2014-06-17 3:06 ` Tsutomu Itoh
2014-06-17 4:48 ` Chris Mason
2014-07-09 17:14 ` James Cloos [this message]
2014-06-17 4:52 ` Tsutomu Itoh
2014-06-17 1:11 ` Chris Mason
2014-06-17 1:36 ` Tsutomu Itoh
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=m3egxu314i.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).