From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: fstests@vger.kernel.org
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
guaneryu@gmail.com, darrick.wong@oracle.com,
linux-xfs@vger.kernel.org
Subject: [PATCH V3 05/19] Fix xfs/127 to work with 64k block size
Date: Wed, 12 Sep 2018 11:56:12 +0530 [thread overview]
Message-ID: <20180912062626.14349-6-chandan@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180912062626.14349-1-chandan@linux.vnet.ibm.com>
With reflink feature enabled, we require atleast 500MiB of
disk space to create a filesystem with 64k block size. Hence this commit
sets the size of the scratch filesystem to 512MiB.
Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
---
tests/xfs/127 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/127 b/tests/xfs/127
index 41dacd7..6a95026 100755
--- a/tests/xfs/127
+++ b/tests/xfs/127
@@ -34,7 +34,7 @@ _require_no_large_scratch_dev
_require_cp_reflink
echo "Format and mount"
-_scratch_mkfs_sized $((2 * 4096 * 4096)) > $seqres.full 2>&1
+_scratch_mkfs_sized $((512 * 1024 * 1024)) > $seqres.full 2>&1
_scratch_mount >> $seqres.full 2>&1
testdir=$SCRATCH_MNT/test-$seq
--
2.9.5
next prev parent reply other threads:[~2018-09-12 11:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 6:26 [PATCH V3 00/19] Fix tests to work on non-4k block sized fs instances Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 01/19] Fix xfs/009 to work with 64k block size Chandan Rajendra
2018-09-17 22:59 ` Darrick J. Wong
2018-09-18 3:18 ` Theodore Y. Ts'o
2018-09-18 3:27 ` Darrick J. Wong
2018-09-18 6:02 ` Chandan Rajendra
2018-09-18 14:36 ` Darrick J. Wong
2018-09-12 6:26 ` [PATCH V3 02/19] xfs/050: Fix "Push past soft inode limit" case Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 03/19] Fix xfs/050 to work with 64k block size Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 04/19] Fix xfs/074 " Chandan Rajendra
2018-09-12 6:26 ` Chandan Rajendra [this message]
2018-09-12 6:26 ` [PATCH V3 06/19] Fix xfs/139 " Chandan Rajendra
2018-09-17 22:29 ` Darrick J. Wong
2018-09-18 8:46 ` Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 07/19] Fix xfs/140 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 08/19] Fix xfs/190 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 09/19] Fix xfs/299 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 10/19] xfs/325: Inject free_extent error after CoW operation Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 11/19] Fix generic/102 to work with 64k block size Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 12/19] Fix generic/172 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 13/19] Filter fiemap output by FS " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 14/19] Fix generic/177 to work with 64k " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 15/19] Fix generic/230 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 16/19] Fix generic/235 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 17/19] Fix generic/459 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 18/19] Fix generic/018 " Chandan Rajendra
2018-09-12 6:26 ` [PATCH V3 19/19] Fix generic/108 " Chandan Rajendra
2018-09-18 5:20 ` [PATCH V3 00/19] Fix tests to work on non-4k block sized fs instances Zorro Lang
2018-09-18 10:28 ` Chandan Rajendra
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=20180912062626.14349-6-chandan@linux.vnet.ibm.com \
--to=chandan@linux.vnet.ibm.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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).