archive mirror
 help / color / mirror / Atom feed
From: Chris Dunlop <>
To: Dave Chinner <>
Cc: Eric Sandeen <>,
Subject: Mysterious ENOSPC [was: XFS fallocate implementation incorrectly reports ENOSPC]
Date: Sat, 28 Aug 2021 10:21:37 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210827220343.GQ3657114@dread.disaster.area>

On Sat, Aug 28, 2021 at 08:03:43AM +1000, Dave Chinner wrote:
> On Fri, Aug 27, 2021 at 04:53:47PM +1000, Chris Dunlop wrote:
>> On 8/25/21 9:06 PM, Chris Dunlop wrote:
>>> Background: I'm chasing a mysterious ENOSPC error on an XFS
>>> filesystem with way more space than the app should be asking
>>> for. There are no quotas on the fs. Unfortunately it's a third
>>> party app and I can't tell what sequence is producing the error,
>>> but this fallocate issue is a possibility.
>> Oh, another reference: this is extensive reflinking happening on this
>> filesystem.
> Ah. Details that are likely extremely important. The workload,
> layout problems and ephemeral ENOSPC symptoms match the description
> of the problem that was fixed by the series of commits that went
> into 5.13 that ended in this one:
> commit fd43cf600cf61c66ae0a1021aca2f636115c7fcb
> Author: Brian Foster <>
> Date:   Wed Apr 28 15:06:05 2021 -0700
>    xfs: set aside allocation btree blocks from block reservation

Oh wow. Yes, sounds like a candidate. Is there same easy(-ish?) way of 
seeing if this fs is likely to be suffering from this particular issue or 
is it a matter of installing an appropriate kernel and seeing if the 
problem goes away?

The job getting this ENOSPC error is one of 45 similar jobs, and it's the 
only one getting the error. There doesn't seem to be anything special 
about this job, it's main file where the writes are going is the 9th 
largest (up to 1.8T), and it has a lot of extents (842G split into 750M 
extents) but not as many as some others (e.g. 809G split into 1G extents).  
That said, the app works in mysterious ways so this particular job may be 
a special snowflake in some unobvious manner.



  reply	other threads:[~2021-08-28  0:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  2:06 XFS fallocate implementation incorrectly reports ENOSPC Chris Dunlop
2021-08-26 15:05 ` Eric Sandeen
2021-08-26 20:56   ` Chris Dunlop
2021-08-27  2:55     ` Chris Dunlop
2021-08-27  5:49       ` Dave Chinner
2021-08-27  6:53         ` Chris Dunlop
2021-08-27 22:03           ` Dave Chinner
2021-08-28  0:21             ` Chris Dunlop [this message]
2021-08-28  3:58               ` Mysterious ENOSPC [was: XFS fallocate implementation incorrectly reports ENOSPC] Chris Dunlop
2021-08-29 22:04                 ` Dave Chinner
2021-08-30  4:21                   ` Darrick J. Wong
2021-08-30  7:40                     ` Chris Dunlop
2021-08-30  7:37                   ` Mysterious ENOSPC Chris Dunlop
2021-09-02  1:42                     ` Dave Chinner
2021-09-17  6:07                       ` Chris Dunlop

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Mysterious ENOSPC [was: XFS fallocate implementation incorrectly reports ENOSPC]' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).