From: Eric Sandeen <sandeen@sandeen.net>
To: sekharan@us.ibm.com
Cc: XFS Mailing List <xfs@oss.sgi.com>
Subject: Re: Failure of test case 244
Date: Tue, 14 Jun 2011 14:38:06 -0500 [thread overview]
Message-ID: <4DF7B89E.8010000@sandeen.net> (raw)
In-Reply-To: <1308076910.7661.470.camel@chandra-lucid.beaverton.ibm.com>
On 6/14/11 1:41 PM, Chandra Seetharaman wrote:
> Hello,
>
> test case 244 expects a mkfs option projid32bit, which is not present in
> older version of mkfs.xfs(for example 3.1.1 in RHEL 6.1).
>
> I though of making it a "requires" for this test, so that the test case
> doesn't generate a "failure" when the test is run on older versions.
>
> Opinions ?
Yes, that make sense; care to send a patch with proper signoff?
Thanks,
-Eric
> regards
>
> chandra
>
> PS: here is the test o/p
>
> FSTYP -- xfs (non-debug)
> PLATFORM -- Linux/x86_64 elm3c201 2.6.39-rc4-xfs.git.p2+
> MKFS_OPTIONS -- -f -bsize=4096 /dev/sdd2
> MOUNT_OPTIONS -- -o context=system_u:object_r:nfs_t:s0 /dev/sdd2 /mnt/xfsScratchMntPt
>
> 244 [failed, exit status 1] - output mismatch (see 244.out.bad)
> --- 244.out 2011-04-20 08:34:36.000000000 -0700
> +++ 244.out.bad 2011-06-14 11:29:57.000000000 -0700
> @@ -1,2 +1,25 @@
> QA output created by 244
> -Silence is golden
> +unknown option -i projid32bit=0
> +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),
> + sectlog=n|sectsize=num
> +/* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2]
> +/* 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=2|ci]
> +/* 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).
> +mkfs failed
> +(see 244.full for details)
> Ran: 244
> Failures: 244
> Failed 1 of 1 tests
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-14 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:41 Failure of test case 244 Chandra Seetharaman
2011-06-14 19:38 ` Eric Sandeen [this message]
2011-06-14 20:10 ` Chandra Seetharaman
2011-06-14 21:08 ` Chandra Seetharaman
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=4DF7B89E.8010000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=sekharan@us.ibm.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 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.