From: Andi Kleen <andi@firstfloor.org>
To: linux-xfs@vger.kernel.org, darrick.wong@oracle.com
Subject: XFS long delays on disk full
Date: Wed, 18 Jul 2018 14:22:40 -0700 [thread overview]
Message-ID: <20180718212240.vxl33543lrh7vgzz@two.firstfloor.org> (raw)
Hi,
I was doing some testing on a 4.18-rc1 kernel, and a single threaded
test wrote a fairly large file to a XFS file system, causing it to
fill up.
After that the process hung in D state for a long time, and only
recovered after several minutes. Here's the backtrace during
the hang:
[<0>] wb_wait_for_completion+0x5e/0x90
[<0>] sync_inodes_sb+0xc9/0x290
[<0>] xfs_flush_inodes+0x25/0x30 [xfs]
[<0>] xfs_file_buffered_aio_write+0x2be/0x300 [xfs]
[<0>] __vfs_write+0x114/0x1a0
[<0>] vfs_write+0xad/0x1a0
[<0>] ksys_write+0x52/0xc0
[<0>] do_syscall_64+0x5b/0x160
[<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[<0>] 0xffffffffffffffff
There were no IO errors or similar.
Expected? Already fixed?
Thanks,
-Andi
next reply other threads:[~2018-07-18 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 21:22 Andi Kleen [this message]
2018-07-18 23:25 ` XFS long delays on disk full Darrick J. Wong
2018-07-20 17:58 ` Andi Kleen
2018-07-24 18:16 ` Darrick J. Wong
2018-07-25 17:00 ` Andi Kleen
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=20180718212240.vxl33543lrh7vgzz@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.