linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Henderson <achender@linux.vnet.ibm.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	xfs@oss.sgi.com
Cc: Allison Henderson <achender@linux.vnet.ibm.com>
Subject: [PATCH 0/2 v8] XFS TESTS: ENOSPC Punch Hole Test
Date: Sun, 17 Jul 2011 16:52:44 -0700	[thread overview]
Message-ID: <1310946766-30217-1-git-send-email-achender@linux.vnet.ibm.com> (raw)

This patch set adds the ENOSPC test that was used for ext4 punch hole testing.
This test will verify that a hole can be punched even when the disk is full.
Reserved blocks should be used to complete the operation when there is not blocks
to further fragment the file.

Because punching a hole does not always require extra blocks, there needs to 
be several iterations of punching holes, and then filling the file system to 100% 
usage before it is forced to grow the tree in order to handle the fragmentation. 
The growing of the tree is what would cause ENOSPC if not for the use of reserved blocks.

Allison Henderson (2):
  XFS TESTS: ENOSPC Punch Hole: Move su routines in 123 to common.rc
  XFS TESTS: Add ENOSPC Hole Punch Test

 123       |   24 ------------
 256       |  120 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 256.out   |    1 +
 common.rc |   81 +++++++++++++++++++++++++++++++++++++++++
 group     |   12 ++++--
 5 files changed, 210 insertions(+), 28 deletions(-)
 create mode 100644 256
 create mode 100644 256.out


             reply	other threads:[~2011-07-17 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 23:52 Allison Henderson [this message]
2011-07-17 23:52 ` [PATCH 1/2 v8] XFS TESTS: ENOSPC Punch Hole: Move su routines in 123 to common.rc Allison Henderson
2011-07-17 23:52 ` [PATCH 2/2 v8] XFS TESTS: Add ENOSPC Hole Punch Test Allison Henderson
2011-07-18 22:09 ` [PATCH 0/2 v8] XFS TESTS: ENOSPC Punch Hole Test Alex Elder
2011-07-19  0:09   ` Allison Henderson

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=1310946766-30217-1-git-send-email-achender@linux.vnet.ibm.com \
    --to=achender@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).