From: Jan Tulak <jtulak@redhat.com>
To: fstests@vger.kernel.org
Cc: Jan Tulak <jtulak@redhat.com>
Subject: [PATCH] xfstests: update xfs/096 for new behaviour
Date: Thu, 2 Jun 2016 11:10:59 +0200 [thread overview]
Message-ID: <1464858659-610-1-git-send-email-jtulak@redhat.com> (raw)
Because we recently changed how mkfs behaves when it gets incorrect/invalid
values, update the expected output to reflect the change.
Signed-off-by: Jan Tulak <jtulak@redhat.com>
---
tests/xfs/096.out.internal | 60 +++++++++++++++++++++++++++++++++++++++-------
1 file changed, 52 insertions(+), 8 deletions(-)
diff --git a/tests/xfs/096.out.internal b/tests/xfs/096.out.internal
index 80201d2..82c2043 100644
--- a/tests/xfs/096.out.internal
+++ b/tests/xfs/096.out.internal
@@ -2,18 +2,62 @@ QA output created by 096
# su too big but must be a multiple of fs block size too
--- mkfs=-l version=2,su=262656 ---
-log stripe unit (262656) must be a multiple of the block size (4096)
+Illegal value 262656 for -l su option. value is too large
+Usage: mkfs.xfs
+/* blocksize */ [-b log=n|size=num]
+/* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num,
+ (sunit=value,swidth=value|su=num,sw=num|noalign),
+ sectlog=n|sectsize=num
+/* force overwrite */ [-f]
+/* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
+ projid32bit=0|1,sparse=0|1]
+/* no discard */ [-K]
+/* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n
+ sunit=value|su=num,sectlog=n|sectsize=num,
+ lazy-count=0|1]
+/* label */ [-L label (maximum 12 characters)]
+/* naming */ [-n log=n|size=num,version=N|ci,ftype=0|1]
+/* no-op info only */ [-N]
+/* prototype file */ [-p fname]
+/* quiet */ [-q]
+/* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx]
+/* sectorsize */ [-s log=n|size=num]
+/* version */ [-V]
+ devicename
+<devicename> is required unless -d name=xxx is given.
+<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
+ xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
+<value> is xxx (512 byte blocks).
# test log stripe greater than LR size
--- mkfs=-l version=2,su=266240 ---
-meta-data=DEV isize=N agcount=N, agsize=N blks
-data = bsize=4096 blocks=N, imaxpct=N
- = sunit=0 swidth=0 blks, unwritten=1
-naming =version 2 bsize=4096
-log =LOG bsize=4096 blocks=N, version=N
- = sunit=N blks
-realtime =REALTIME extsz=N, blocks=N, rtextents=N
+Illegal value 266240 for -l su option. value is too large
+Usage: mkfs.xfs
+/* blocksize */ [-b log=n|size=num]
+/* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num,
+ (sunit=value,swidth=value|su=num,sw=num|noalign),
+ sectlog=n|sectsize=num
+/* force overwrite */ [-f]
+/* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
+ projid32bit=0|1,sparse=0|1]
+/* no discard */ [-K]
+/* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n
+ sunit=value|su=num,sectlog=n|sectsize=num,
+ lazy-count=0|1]
+/* label */ [-L label (maximum 12 characters)]
+/* naming */ [-n log=n|size=num,version=N|ci,ftype=0|1]
+/* no-op info only */ [-N]
+/* prototype file */ [-p fname]
+/* quiet */ [-q]
+/* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx]
+/* sectorsize */ [-s log=n|size=num]
+/* version */ [-V]
+ devicename
+<devicename> is required unless -d name=xxx is given.
+<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
+ xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
+<value> is xxx (512 byte blocks).
# same test but get log stripe from data stripe
--
2.5.5
next reply other threads:[~2016-06-02 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 9:10 Jan Tulak [this message]
2016-06-07 3:45 ` [PATCH] xfstests: update xfs/096 for new behaviour Eryu Guan
[not found] ` <CACj3i733G7oz_tg4NANfz_=X5nYMp31k-FskEPXxHsaSxKtTEw@mail.gmail.com>
2016-06-07 8:31 ` Fwd: " Jan Tulak
2016-06-23 11:22 ` Jan Tulak
2016-06-23 11:41 ` Jan Tulak
2016-06-29 10:18 ` [PATCH v2] " Jan Tulak
2016-06-30 6:54 ` Eryu Guan
2016-07-01 0:37 ` Dave Chinner
2016-07-01 3:05 ` Eryu Guan
2016-07-01 12:12 ` Jan Tulak
2016-07-01 16:14 ` [PATCH v3] " Jan Tulak
2016-07-13 10:38 ` Eryu Guan
2016-07-14 10:25 ` Jan Tulak
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=1464858659-610-1-git-send-email-jtulak@redhat.com \
--to=jtulak@redhat.com \
--cc=fstests@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