From: Alex Elder <aelder@sgi.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<xfs@oss.sgi.com>
Subject: Re: [PATCH 0/2 v8] XFS TESTS: ENOSPC Punch Hole Test
Date: Mon, 18 Jul 2011 17:09:13 -0500 [thread overview]
Message-ID: <1311026953.2790.49.camel@doink> (raw)
In-Reply-To: <1310946766-30217-1-git-send-email-achender@linux.vnet.ibm.com>
On Sun, 2011-07-17 at 16:52 -0700, Allison Henderson wrote:
> 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.
I have reviewed both of your updated patches. They
both look good to me. I'll give it another day or
two for others to comment if they like, but unless
someone suggests changes I'll commit this for you.
Reviewed-by: Alex Elder <aelder@sgi.com>
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-18 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 23:52 [PATCH 0/2 v8] XFS TESTS: ENOSPC Punch Hole Test Allison Henderson
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 ` Alex Elder [this message]
2011-07-19 0:09 ` [PATCH 0/2 v8] XFS TESTS: ENOSPC Punch Hole Test 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=1311026953.2790.49.camel@doink \
--to=aelder@sgi.com \
--cc=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).