* 3.5.2: moving files from xfs/disk -> nfs: radix_tree_lookup_slot+0xe/0x10
@ 2012-08-27 15:00 Justin Piszcz
2012-09-01 23:13 ` Christoph Hellwig
0 siblings, 1 reply; 3+ messages in thread
From: Justin Piszcz @ 2012-08-27 15:00 UTC (permalink / raw)
To: linux-kernel; +Cc: xfs
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.705697] INFO: task sync:8790 blocked for more than 120 seconds.
[75716.705701] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[75716.705703] sync D ffff88040ec54830 0 8790 2141 0x00000000
[75716.705708] ffff88001fff1d08 0000000000000086 ffffffff81862fc0
ffff88001fff1fd8
[75716.705713] ffff88001fff1fd8 0000000000004000 ffff88041d958670
ffff88040ec54830
[75716.705716] ffff88001fff1c38 ffffffff812dcaee ffff88001fff1c58
ffff88001fff1d78
[75716.705720] Call Trace:
[75716.705729] [<ffffffff812dcaee>] ? radix_tree_lookup_slot+0xe/0x10
[75716.705733] [<ffffffff81082ca6>] ? find_get_pages_tag+0xc6/0x150
[75716.705738] [<ffffffff81057980>] ? __enqueue_entity+0x70/0x80
[75716.705742] [<ffffffff810e3450>] ? __sync_filesystem+0x90/0x90
[75716.705747] [<ffffffff815a3d04>] schedule+0x24/0x70
[75716.705751] [<ffffffff815a2549>] schedule_timeout+0x1a9/0x210
[75716.705755] [<ffffffff81089550>] ? calc_period_shift+0x60/0x60
[75716.705760] [<ffffffff81052ef5>] ? check_preempt_curr+0x75/0xa0
[75716.705764] [<ffffffff815a3420>] wait_for_common+0xc0/0x150
[75716.705767] [<ffffffff81055af0>] ? try_to_wake_up+0x280/0x280
[75716.705770] [<ffffffff810e3450>] ? __sync_filesystem+0x90/0x90
[75716.705773] [<ffffffff815a3d78>] wait_for_completion+0x18/0x20
[75716.705777] [<ffffffff810dfa47>] writeback_inodes_sb_nr+0x77/0xa0
[75716.705782] [<ffffffff810d0101>] ?
shrink_dcache_for_umount_subtree+0x111/0x1d0
[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.
Thoughts?
Justin.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 3.5.2: moving files from xfs/disk -> nfs: radix_tree_lookup_slot+0xe/0x10
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
0 siblings, 1 reply; 3+ messages in thread
From: Christoph Hellwig @ 2012-09-01 23:13 UTC (permalink / raw)
To: Justin Piszcz; +Cc: linux-kernel, xfs, linux-m
I'd suspect it's something with the actual radix tree code, Ccing
linux-mm in case they know more.
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.705697] INFO: task sync:8790 blocked for more than 120 seconds.
> [75716.705701] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [75716.705703] sync D ffff88040ec54830 0 8790 2141 0x00000000
> [75716.705708] ffff88001fff1d08 0000000000000086 ffffffff81862fc0
> ffff88001fff1fd8
> [75716.705713] ffff88001fff1fd8 0000000000004000 ffff88041d958670
> ffff88040ec54830
> [75716.705716] ffff88001fff1c38 ffffffff812dcaee ffff88001fff1c58
> ffff88001fff1d78
> [75716.705720] Call Trace:
> [75716.705729] [<ffffffff812dcaee>] ? radix_tree_lookup_slot+0xe/0x10
> [75716.705733] [<ffffffff81082ca6>] ? find_get_pages_tag+0xc6/0x150
> [75716.705738] [<ffffffff81057980>] ? __enqueue_entity+0x70/0x80
> [75716.705742] [<ffffffff810e3450>] ? __sync_filesystem+0x90/0x90
> [75716.705747] [<ffffffff815a3d04>] schedule+0x24/0x70
> [75716.705751] [<ffffffff815a2549>] schedule_timeout+0x1a9/0x210
> [75716.705755] [<ffffffff81089550>] ? calc_period_shift+0x60/0x60
> [75716.705760] [<ffffffff81052ef5>] ? check_preempt_curr+0x75/0xa0
> [75716.705764] [<ffffffff815a3420>] wait_for_common+0xc0/0x150
> [75716.705767] [<ffffffff81055af0>] ? try_to_wake_up+0x280/0x280
> [75716.705770] [<ffffffff810e3450>] ? __sync_filesystem+0x90/0x90
> [75716.705773] [<ffffffff815a3d78>] wait_for_completion+0x18/0x20
> [75716.705777] [<ffffffff810dfa47>] writeback_inodes_sb_nr+0x77/0xa0
> [75716.705782] [<ffffffff810d0101>] ?
> shrink_dcache_for_umount_subtree+0x111/0x1d0
> [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.
>
> Thoughts?
>
> Justin.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 3.5.2: moving files from xfs/disk -> nfs: radix_tree_lookup_slot+0xe/0x10
2012-09-01 23:13 ` Christoph Hellwig
@ 2012-09-03 5:43 ` Dave Chinner
0 siblings, 0 replies; 3+ messages in thread
From: Dave Chinner @ 2012-09-03 5:43 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Justin Piszcz, linux-m, linux-kernel, xfs
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-09-03 5:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).