From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Running out of reserved data blocks
Date: Fri, 26 Sep 2008 15:31:23 +1000 [thread overview]
Message-ID: <48DC73AB.4050309@sgi.com> (raw)
A while back I posted a patch to re-dirty pages on I/O error to handle errors from
xfs_trans_reserve() that was failing with ENOSPC when trying to convert delayed
allocations. I'm now seeing xfs_trans_reserve() fail when converting unwritten
extents and in that case we silently ignore the error and leave the extent as
unwritten which effectively causes data corruption. I can also get failures when
trying to unreserve disk space.
I've tried increasing the size of the reserved data blocks pool but that only
delays the inevitable. Increasing the size to 65536 blocks seems to avoid failures
but that's getting to be a lot of disk space.
All of these ENOSPC errors should be transient and if we retried the operation - or
waited for the reserved pool to refill - we could proceed with the transaction. I
was thinking about adding a retry loop in xfs_trans_reserve() so if XFS_TRANS_RESERVE
is set and we fail to get space we just keep trying. It's not very elegant but saves
having to address the ENOSPC failure in many code paths.
Does anyone have any other suggestions?
Lachlan
next reply other threads:[~2008-09-26 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 5:31 Lachlan McIlroy [this message]
2008-09-26 7:08 ` Running out of reserved data blocks Dave Chinner
2008-09-26 7:45 ` Lachlan McIlroy
2008-09-26 8:48 ` Dave Chinner
2008-09-29 2:44 ` Lachlan McIlroy
2008-09-29 6:51 ` Dave Chinner
2008-09-29 8:40 ` Lachlan McIlroy
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=48DC73AB.4050309@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs-dev@sgi.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