From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfstests: use minimum log size in xfs/016
Date: Fri, 18 Oct 2013 13:16:14 -0400 [thread overview]
Message-ID: <1382116574-7766-1-git-send-email-bfoster@redhat.com> (raw)
Test xfs/016 fails to run due to invalid mkfs options. The log size
is reported as too small according to the minimum log size
calculation:
log size 512 blocks too small, minimum size is 853 blocks
Update log_size to the currently specified minimum.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
tests/xfs/016 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/xfs/016 b/tests/xfs/016
index 2fc6af2..e52f80c 100755
--- a/tests/xfs/016
+++ b/tests/xfs/016
@@ -181,7 +181,7 @@ _supported_os Linux
rm -f $seqres.full
# mkfs sizes
-log_size=2097152
+log_size=3493888
log_size_bb=`expr $log_size / 512`
_require_scratch
--
1.8.1.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-10-18 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 17:16 Brian Foster [this message]
2013-10-18 22:58 ` [PATCH] xfstests: use minimum log size in xfs/016 Dave Chinner
2013-10-22 21:13 ` Rich Johnston
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=1382116574-7766-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--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