* XFS trouble: task xfssyncd blocked for more than 120 seconds.
@ 2009-01-27 17:33 Julian Einwag
2009-01-28 18:32 ` Russell Cattelan
0 siblings, 1 reply; 3+ messages in thread
From: Julian Einwag @ 2009-01-27 17:33 UTC (permalink / raw)
To: xfs
Hi,
we're currently using XFS on our POP/IMAP server for storage of the
user's mailboxes (Linux kernel version 2.6.27.10, x86_64).
Howevere, we're experencing some seemingly random filesystem lockups
during which the filesystem can still be read, but not written. The
following error messages show in in the system logs:
Jan 27 17:03:01 postman-64b kernel: "echo 0 > /proc/sys/kernel/
hung_task_timeout_secs" disables this message.
Jan 27 17:03:01 postman-64b kernel: xfssyncd D
0000000100921c06 0 3090 2
Jan 27 17:03:01 postman-64b kernel: ffff88067b1cbd70 0000000000000046
0000000000000000 0000000000000001
Jan 27 17:03:01 postman-64b kernel: ffff88067a6124c0 ffff88067cc7c980
ffff88067a612718 00000002a8421200
Jan 27 17:03:01 postman-64b kernel: 00000000fffffffd 0000000000001000
0000000000000000 0000000000000001
Jan 27 17:03:01 postman-64b kernel: Call Trace:
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8041d432>]
schedule_timeout+0x1e/0xad
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01ce88e>]
xfs_buf_iorequest+0x5d/0x61 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d2352>]
xfs_bdstrat_cb+0x36/0x3a [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8041c9e4>]
wait_for_common+0xc8/0x132
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8022b373>]
default_wake_function+0x0/0xe
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c70ba>]
xfs_finish_reclaim+0x110/0x13b [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c7169>]
xfs_finish_reclaim_all+0x84/0xc9 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c634b>] xfs_syncsub
+0x4c/0x226 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d3d54>]
xfs_sync_worker+0x17/0x36 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d4cb3>] xfssyncd
+0x133/0x182 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d4b80>] xfssyncd
+0x0/0x182 [xfs]
Jan 27 17:03:01 postman-64b kernel: [<ffffffff80244a68>] kthread
+0x47/0x73
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8022f77f>] schedule_tail
+0x27/0x5f
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8020ccf9>] child_rip
+0xa/0x11
Jan 27 17:03:01 postman-64b kernel: [<ffffffff802f9395>]
generic_unplug_device+0x0/0x2d
Jan 27 17:03:01 postman-64b kernel: [<ffffffff80244a21>] kthread
+0x0/0x73
Jan 27 17:03:01 postman-64b kernel: [<ffffffff8020ccef>] child_rip
+0x0/0x11
Only rebooting helps.
The filesystem is hosted on a hardware-based RAID5 array.
We're currently out of ideas on what might be causing this, so any
hints would be greately appreciated.
Best regards,
Julian Einwag
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: XFS trouble: task xfssyncd blocked for more than 120 seconds.
2009-01-27 17:33 XFS trouble: task xfssyncd blocked for more than 120 seconds Julian Einwag
@ 2009-01-28 18:32 ` Russell Cattelan
2009-02-04 16:27 ` Julian Einwag
0 siblings, 1 reply; 3+ messages in thread
From: Russell Cattelan @ 2009-01-28 18:32 UTC (permalink / raw)
To: Julian Einwag; +Cc: xfs
[-- Attachment #1.1: Type: text/plain, Size: 3066 bytes --]
Could get a call trace of all process the next time this happens?
srq-t
That would help us to see what else is going on and what might be
holding things up.
Julian Einwag wrote:
> Hi,
>
> we're currently using XFS on our POP/IMAP server for storage of the
> user's mailboxes (Linux kernel version 2.6.27.10, x86_64).
> Howevere, we're experencing some seemingly random filesystem lockups
> during which the filesystem can still be read, but not written. The
> following error messages show in in the system logs:
>
> Jan 27 17:03:01 postman-64b kernel: "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Jan 27 17:03:01 postman-64b kernel: xfssyncd D
> 0000000100921c06 0 3090 2
> Jan 27 17:03:01 postman-64b kernel: ffff88067b1cbd70 0000000000000046
> 0000000000000000 0000000000000001
> Jan 27 17:03:01 postman-64b kernel: ffff88067a6124c0 ffff88067cc7c980
> ffff88067a612718 00000002a8421200
> Jan 27 17:03:01 postman-64b kernel: 00000000fffffffd 0000000000001000
> 0000000000000000 0000000000000001
> Jan 27 17:03:01 postman-64b kernel: Call Trace:
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8041d432>]
> schedule_timeout+0x1e/0xad
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01ce88e>]
> xfs_buf_iorequest+0x5d/0x61 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d2352>]
> xfs_bdstrat_cb+0x36/0x3a [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8041c9e4>]
> wait_for_common+0xc8/0x132
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8022b373>]
> default_wake_function+0x0/0xe
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c70ba>]
> xfs_finish_reclaim+0x110/0x13b [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c7169>]
> xfs_finish_reclaim_all+0x84/0xc9 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01c634b>]
> xfs_syncsub+0x4c/0x226 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d3d54>]
> xfs_sync_worker+0x17/0x36 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d4cb3>]
> xfssyncd+0x133/0x182 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffffa01d4b80>]
> xfssyncd+0x0/0x182 [xfs]
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff80244a68>]
> kthread+0x47/0x73
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8022f77f>]
> schedule_tail+0x27/0x5f
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8020ccf9>]
> child_rip+0xa/0x11
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff802f9395>]
> generic_unplug_device+0x0/0x2d
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff80244a21>]
> kthread+0x0/0x73
> Jan 27 17:03:01 postman-64b kernel: [<ffffffff8020ccef>]
> child_rip+0x0/0x11
>
> Only rebooting helps.
>
> The filesystem is hosted on a hardware-based RAID5 array.
>
> We're currently out of ideas on what might be causing this, so any
> hints would be greately appreciated.
>
> Best regards,
> Julian Einwag
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: XFS trouble: task xfssyncd blocked for more than 120 seconds.
2009-01-28 18:32 ` Russell Cattelan
@ 2009-02-04 16:27 ` Julian Einwag
0 siblings, 0 replies; 3+ messages in thread
From: Julian Einwag @ 2009-02-04 16:27 UTC (permalink / raw)
To: xfs
Hi!
Am 28.01.2009 um 19:32 schrieb Russell Cattelan:
> Could get a call trace of all process the next time this happens?
>
> srq-t
>
> That would help us to see what else is going on and what might be
> holding things up.
Just wanted to give a quick feedback here: We recently did an upgrade
to Kernel 2.6.28.3 and things have been running smoothly so far, so
we're hoping that the problem is gone.
Best regards,
Julian
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-02-04 16:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-27 17:33 XFS trouble: task xfssyncd blocked for more than 120 seconds Julian Einwag
2009-01-28 18:32 ` Russell Cattelan
2009-02-04 16:27 ` Julian Einwag
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox