From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfstests 217: remove file in between mkfs's
Date: Tue, 08 Jun 2010 22:28:12 -0500 [thread overview]
Message-ID: <4C0F0A4C.7050600@sandeen.net> (raw)
217 requires a 2G scratch:
_require_fs_space $SCRATCH_MNT 2202000
but as we mkfs different sizes, we actually are filling in the
sparse loopback more and more, and 3.8G isn't enough to contain it.
If we remove & recreate the file between mkfs's it doesn't take
so much space ... I don't think it adds significantly to test time.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
diff --git a/217 b/217
index 19540ad..ed86a51 100755
--- a/217
+++ b/217
@@ -60,6 +60,9 @@ LOOP_MNT=$SCRATCH_MNT/test_fs_dir
_do_mkfs()
{
for i in $*; do
+ # make large holey file
+ rm -f $LOOP_DEV
+ $XFS_IO_PROG -f -c "truncate 16383g" $LOOP_DEV
echo -n "fssize=${i}g "
$MKFS_XFS_PROG -f -b size=4096 -l version=2 \
-d name=$LOOP_DEV,size=${i}g |grep log
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-06-09 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 3:28 Eric Sandeen [this message]
2010-06-09 13:25 ` [PATCH] xfstests 217: remove file in between mkfs's Christoph Hellwig
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=4C0F0A4C.7050600@sandeen.net \
--to=sandeen@sandeen.net \
--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