From: Eric Sandeen <sandeen@sandeen.net>
To: xfs mailing list <xfs@oss.sgi.com>
Subject: [PATCH] xfstests: fix up features2 tests for lazy-count=1
Date: Tue, 21 Apr 2009 15:25:31 -0500 [thread overview]
Message-ID: <49EE2BBB.3070008@sandeen.net> (raw)
A few more tests are unhappy with a lazy-count=1 change;
specify lazy-count=0 in them for these tests.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/186 b/186
index e8706e4..3e487ab 100755
--- a/186
+++ b/186
@@ -135,7 +135,7 @@ _supported_os Linux
_require_scratch
rm -f $seq.full
-_scratch_mkfs -i attr=2,size=512 >/dev/null 2>&1
+_scratch_mkfs -i attr=2,size=512 -l lazy-count=0 >/dev/null 2>&1
# set inum to root dir ino
# we'll add in dirents and EAs into the root directory
diff --git a/187 b/187
index 4e79055..8ae3ef9 100755
--- a/187
+++ b/187
@@ -54,7 +54,7 @@ export MOUNT_OPTIONS=""
# Make sure that when we think we are testing with morebits off
# that we really are.
# Trying to future-proof in case mkfs defaults change.
-_scratch_mkfs -i attr=1 >/dev/null 2>&1
+_scratch_mkfs -i attr=1 -l lazy-count=0 >/dev/null 2>&1
$XFS_DB_PROG -c version $SCRATCH_DEV 2>&1 >$tmp.db
if grep -i morebits $tmp.db
then
diff --git a/199 b/199
index 099cc1c..c7dcbdd 100644
--- a/199
+++ b/199
@@ -35,7 +35,7 @@ _supported_os Linux
_require_scratch
-_scratch_mkfs_xfs >/dev/null 2>&1
+_scratch_mkfs_xfs -l lazy-count=0>/dev/null 2>&1
#
# Print the current flags. Just a dummy so that the test breaks
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-04-21 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 20:25 Eric Sandeen [this message]
2009-04-23 17:15 ` [PATCH] xfstests: fix up features2 tests for lazy-count=1 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=49EE2BBB.3070008@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.