From: WuBo <wu.bo@cn.fujitsu.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfstests 264: add a copy and reserve test
Date: Thu, 03 Nov 2011 16:04:43 +0800 [thread overview]
Message-ID: <4EB24B1B.2030304@cn.fujitsu.com> (raw)
In-Reply-To: <20111103065525.GA6800@infradead.org>
On 11/03/2011 02:55 PM, Christoph Hellwig wrote:
> On Thu, Nov 03, 2011 at 11:08:55AM +0800, WuBo wrote:
>> This test is a stress test. It creates a set of threads for coping small files
>> into disk. I use a 2G disk for test, the ENOSPC arises usually but the disk is
>> not full under kenerl 3.0 with intel64.
>
> It seems like you really want to use _scratch_mkfs_sized instead of the
> btrfs-specific resize option and make the test generic. Also we already
OK, thanks for _scratch_mkfs_sized, It's will make these tests generic.
> have used up these test numbers in the xfstests-dev repository, and I
> will commit another batch of tests today.
I will change my test numbers in next version.
thanks,
wubo
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" 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-11-03 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 3:05 [PATCH 0/3] xfstests: Add a group of reservation space test WuBo
2011-11-03 3:08 ` [PATCH 1/3] xfstests 264: add a copy and reserve test WuBo
2011-11-03 6:55 ` Christoph Hellwig
2011-11-03 8:04 ` WuBo [this message]
2011-11-03 3:09 ` [PATCH 2/3] xfstests 265: add a prealloc " WuBo
2011-11-15 18:21 ` Ben Myers
2011-11-15 19:08 ` Christoph Hellwig
2011-11-16 1:30 ` WuBo
2011-11-03 3:09 ` [PATCH 3/3] xfstests 266: add a write " WuBo
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=4EB24B1B.2030304@cn.fujitsu.com \
--to=wu.bo@cn.fujitsu.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@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).