linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Todd Gill <tgill@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: file write that exceeds thin device capacity
Date: Tue, 13 Nov 2018 14:57:18 -0500	[thread overview]
Message-ID: <18125274-1c2e-6171-a597-4e2ffb165162@redhat.com> (raw)

Hi,

This script creates a 1 TB thin device (device mapper)  backed by 1 GB
of physical space.  The script then writes more than 1 GB via
$BLOCK_SIZE files to XFS.  I'm testing to see if recovery can be
automated.

https://paste.fedoraproject.org/paste/ropelNyOQWCjk3hfK0jltA

When the $BLOCK_SIZE passed to dd is 4k - dd gets an error on the file
write that exceeds the physical capacity that backs the thin device.
XFS doesn't indicate any problems.

If I set the $BLOCK_SIZE to 32k - I see entries in the system log that
indicate XFS loops retrying the writes.

Is that expected?  Is it just more likely to happen with larger block
sizes?

I’m looking to understand how to recover when a thin device runs out of
space under XFS.

Example system log entries:

[  +5.048997] XFS (dm-3): metadata I/O error: block 0xf0000
("xfs_buf_iodone_callback_error") error 28 numblks 32
[  +1.376913] XFS: Failing async write: 1164 callbacks suppressed
[  +0.000004] XFS (dm-3): Failing async write on buffer block 0xf0020.
Retrying async write.

Thanks for any help,
Todd

             reply	other threads:[~2018-11-14  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 19:57 Todd Gill [this message]
2018-11-13 22:10 ` file write that exceeds thin device capacity Dave Chinner
2018-11-15 22:22   ` Eric Sandeen

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=18125274-1c2e-6171-a597-4e2ffb165162@redhat.com \
    --to=tgill@redhat.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 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).