linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-m@kvack.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 3.5.2: moving files from xfs/disk -> nfs: radix_tree_lookup_slot+0xe/0x10
Date: Mon, 3 Sep 2012 15:43:27 +1000	[thread overview]
Message-ID: <20120903054327.GZ15292@dastard> (raw)
In-Reply-To: <20120901231338.GE6896@infradead.org>

On Sat, Sep 01, 2012 at 07:13:38PM -0400, Christoph Hellwig wrote:
> I'd suspect it's something with the actual radix tree code, Ccing
> linux-mm in case they know more.

I don't think it has anything to do with the radix tree code....

> On Mon, Aug 27, 2012 at 11:00:10AM -0400, Justin Piszcz wrote:
> > Hi,
> > 
> > Moving ~276GB of files (mainly large backups) and everything has
> > seemed to lockup on the client moving data to the server, it is still
> > in this state..
.....

> > [75716.705720] Call Trace:
> > [75716.705729]  [<ffffffff812dcaee>] ? radix_tree_lookup_slot+0xe/0x10

It's just a symbol that was found in the stack. The real trace is
this:

> > [75716.705747]  [<ffffffff815a3d04>] schedule+0x24/0x70
> > [75716.705751]  [<ffffffff815a2549>] schedule_timeout+0x1a9/0x210
> > [75716.705764]  [<ffffffff815a3420>] wait_for_common+0xc0/0x150
> > [75716.705773]  [<ffffffff815a3d78>] wait_for_completion+0x18/0x20
> > [75716.705777]  [<ffffffff810dfa47>] writeback_inodes_sb_nr+0x77/0xa0
> > [75716.705785]  [<ffffffff810dfa99>] writeback_inodes_sb+0x29/0x40
> > [75716.705788]  [<ffffffff810e3407>] __sync_filesystem+0x47/0x90
> > [75716.705791]  [<ffffffff810e346b>] sync_one_sb+0x1b/0x20
> > [75716.705795]  [<ffffffff810bea71>] iterate_supers+0xe1/0xf0
> > [75716.705798]  [<ffffffff810e355b>] sys_sync+0x2b/0x60
> > [75716.705802]  [<ffffffff815a53a6>] system_call_fastpath+0x1a/0x1f
> > [75836.701197] INFO: task sync:8790 blocked for more than 120 seconds.

Which simply says that writeback of the dirty data at the time of
the sync call has taken longer than 120s.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2012-09-03  5:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 15:00 3.5.2: moving files from xfs/disk -> nfs: radix_tree_lookup_slot+0xe/0x10 Justin Piszcz
2012-09-01 23:13 ` Christoph Hellwig
2012-09-03  5:43   ` Dave Chinner [this message]

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=20120903054327.GZ15292@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m@kvack.org \
    --cc=xfs@oss.sgi.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).