linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 62751] INFO: rcu_sched detected stalls on CPUs/tasks: { 3} (detected by 2, t=15107 jiffies, g=270766, c=270765, q=0)
Date: Sat, 07 Dec 2013 10:08:16 +0000	[thread overview]
Message-ID: <bug-62751-13602-lZWhRkeGnY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62751-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=62751

Zheng Liu <gnehzuil.liu@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gnehzuil.liu@gmail.com

--- Comment #10 from Zheng Liu <gnehzuil.liu@gmail.com> ---
Hi Loris,

Sorry for my late reply.  I haven't had a chance to take a closer look at this
problem until now.

(In reply to Loris Luise from comment #8)
> Hello,
> 
> what can I do on my side?

I am not sure whether you use 'delalloc' on your system.  I don't see these
details from the log that you pasted.  So now only I could suggest is that you
can try to turn off the delalloc.  The step is as below:

 % sudo mount -t ext4 -o remount,nodelalloc ${DEV} ${MNT}

After this, it won't track the delayed entry on extent status tree.  So it will
avoid es shrinker to take too much time to scan delayed entries that couldn't
be reclaimed.

Then I will try to reproduce this problem on my sand box and think about how to
improve es shrinker.

Thanks,
- Zheng

> 
> I've done the following modifications:
> 
> 1) Installed latest mainline kernel 3.12
> 
> 2) Replaced SCSI drivers from vmw_pvsci to LSI Logic SAS (mptsas)
> 
> 3) reduced number of CPUs from 8 to 4
> 
> 4) enabled on ESXi (4.1) setting for this machine "CPU Hot add" feature
> 
> The issue is still affecting ths machine... other 2 almost equals machine
> running on this host (same kernel) but with XFS on root are not affected and
> very
> stable.
> 
> I reattached another info file (bug-20131118084007.txt) which contains a lot
> of infos.
> 
> Thanks.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-12-07 10:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 13:55 [Bug 62751] New: INFO: rcu_sched detected stalls on CPUs/tasks: { 3} (detected by 2, t=15107 jiffies, g=270766, c=270765, q=0) bugzilla-daemon
2013-10-09 13:59 ` [Bug 62751] " bugzilla-daemon
2013-10-09 15:10 ` bugzilla-daemon
2013-10-09 20:53 ` bugzilla-daemon
2013-10-10  6:49 ` bugzilla-daemon
2013-10-10  6:56 ` bugzilla-daemon
2013-10-24  8:18 ` bugzilla-daemon
2013-10-24 10:18 ` bugzilla-daemon
2013-11-04 11:53 ` bugzilla-daemon
2013-11-13 13:44 ` bugzilla-daemon
2013-11-18  7:51 ` bugzilla-daemon
2013-11-18  7:53 ` bugzilla-daemon
2013-11-18  7:54 ` bugzilla-daemon
2013-12-07 10:08 ` bugzilla-daemon [this message]
2013-12-20 15:45 ` bugzilla-daemon
2013-12-20 16:16 ` bugzilla-daemon

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=bug-62751-13602-lZWhRkeGnY@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).