From: Dave Chinner <david@fromorbit.com>
To: Bob Mastors <bob.mastors@solidfire.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs umount hang in xfs_ail_push_all_sync on i/o error
Date: Tue, 29 Apr 2014 09:45:58 +1000 [thread overview]
Message-ID: <20140428234558.GD18672@dastard> (raw)
In-Reply-To: <CALjwKZDsGBxTDLvy7-W76FRpHRuki_ZjOXLWZ70fut4hmDkTSQ@mail.gmail.com>
On Mon, Apr 28, 2014 at 04:29:02PM -0600, Bob Mastors wrote:
> Greetings,
>
> I have an xfs umount hang caused by forcing the block device to return
> i/o errors while copying files to the filesystem.
> Detailed steps to reproduce the problem on virtualbox are below.
>
> The linux version is a recent pull and reports as 3.15.0-rc3.
>
> [ 2040.248096] INFO: task umount:10303 blocked for more than 120 seconds.
> [ 2040.323947] Not tainted 3.15.0-rc3 #4
> [ 2040.343423] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
> this message.
> [ 2040.352665] umount D ffffffff8180fe40 0 10303 8691
> 0x00000000
> [ 2040.404918] ffff88001e33dd58 0000000000000086 ffff88001e33dd48
> ffffffff81080f82
> [ 2040.489901] ffff88001b311900 0000000000013180 ffff88001e33dfd8
> 0000000000013180
> [ 2040.534772] ffff88003daa3200 ffff88001b311900 ffff88002421aec0
> ffff88002421ae80
> [ 2040.587450] Call Trace:
> [ 2040.592176] [<ffffffff81080f82>] ? try_to_wake_up+0x232/0x2b0
> [ 2040.620212] [<ffffffff816c54d9>] schedule+0x29/0x70
> [ 2040.627685] [<ffffffffa04c4cd6>] xfs_ail_push_all_sync+0x96/0xd0 [xfs]
> [ 2040.632236] [<ffffffff81092230>] ? __wake_up_sync+0x20/0x20
> [ 2040.659105] [<ffffffffa04731a3>] xfs_unmountfs+0x63/0x160 [xfs]
> [ 2040.691774] [<ffffffffa0478f65>] ? kmem_free+0x35/0x40 [xfs]
> [ 2040.698610] [<ffffffffa0474cf5>] xfs_fs_put_super+0x25/0x60 [xfs]
> [ 2040.706838] [<ffffffff8119561e>] generic_shutdown_super+0x7e/0x100
> [ 2040.723958] [<ffffffff811956d0>] kill_block_super+0x30/0x80
> [ 2040.734963] [<ffffffff8119591d>] deactivate_locked_super+0x4d/0x80
> [ 2040.745485] [<ffffffff8119652e>] deactivate_super+0x4e/0x70
> [ 2040.751274] [<ffffffff811b1d42>] mntput_no_expire+0xd2/0x160
> [ 2040.755894] [<ffffffff811b2fff>] SyS_umount+0xaf/0x3b0
> [ 2040.761032] [<ffffffff816d1592>] system_call_fastpath+0x16/0x1b
> [ .060058] XFS (sdb): xfs_log_force: error 5 returned.
> [ 268059] XFS (sdb): xfs_log_force: error 5 returned.
>
> I took a look at xfs_ail_push_all_sync and it is pretty easy to see
> the hang. But it is not obvious to me how to fix it.
> Any ideas would be appreciated.
>
> I am available to run additional tests or capture more logging
> or whatever if that would help.
What's the entire log output from the first shutdown message?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-04-28 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 22:29 xfs umount hang in xfs_ail_push_all_sync on i/o error Bob Mastors
2014-04-28 23:45 ` Dave Chinner [this message]
2014-04-28 23:51 ` Bob Mastors
2014-04-29 1:01 ` Dave Chinner
2014-04-29 1:11 ` Bob Mastors
[not found] ` <CALjwKZBj0f_y7MPp-PLqhLDOnfmf2OWsvv_vbnX08ubevqM+Bg@mail.gmail.com>
2014-04-30 3:22 ` Dave Chinner
[not found] ` <CALjwKZDeTcOSJDtRcNa3KtLraPKvWUB0jvQrwSANxB0RHds0Rg@mail.gmail.com>
2014-05-03 0:05 ` Dave Chinner
2014-05-03 0:47 ` Bob Mastors
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=20140428234558.GD18672@dastard \
--to=david@fromorbit.com \
--cc=bob.mastors@solidfire.com \
--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