linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS long delays on disk full
Date: Wed, 18 Jul 2018 16:25:33 -0700	[thread overview]
Message-ID: <20180718232533.GC4813@magnolia> (raw)
In-Reply-To: <20180718212240.vxl33543lrh7vgzz@two.firstfloor.org>

On Wed, Jul 18, 2018 at 02:22:40PM -0700, Andi Kleen wrote:
> 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

Hmm, these two:

> [<0>] xfs_flush_inodes+0x25/0x30 [xfs]
> [<0>] xfs_file_buffered_aio_write+0x2be/0x300 [xfs]

Offhand I'd guess (while awayish at OSCON) that the fs hit ENOSPC while
trying to write() the file so now we're scanning the fs like mad trying
to free up space preallocations from any open file in the fs.

How big is the fs, how big is the file, how many inodes, how many are
open, which kernel?

--D

> [<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
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-07-19  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 21:22 XFS long delays on disk full Andi Kleen
2018-07-18 23:25 ` Darrick J. Wong [this message]
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=20180718232533.GC4813@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=andi@firstfloor.org \
    --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 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).