From: Shuang Qiu <shuang.qiu@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] mkfs01 testcases issue
Date: Sat, 26 Dec 2015 01:37:20 +0800 [thread overview]
Message-ID: <567D7ED0.2060706@oracle.com> (raw)
Hi,
While running LTP commands testcases,these three
tests(mkfs01_msdos,mkfs01_vfat,mkswap01) sometimes failed.
It is because that mkfs.vfat/mkswap on the test block device which is
made as btrfs( in previous mkfs01_btrfs test) does not work.
blkid still show "TYPE="btrfs" after mkfs.vfat/mkswap.
Seems the issue is only reproduced with a very small size of block
device(less than 20M).
Does anyone hit similar issue,is it a kernel or btrfs bug?
Anyway,how about making the test block device $LTP_DEV to the original
filesystem in tst_release_device(),so it will avoid such effect between
different testcases.
--- a/testcases/lib/test.sh
+++ b/testcases/lib/test.sh
@@ -253,6 +253,7 @@ tst_acquire_device()
tst_release_device()
{
if [ ${TST_DEVICE_FLAG} -eq 0 ]; then
+ tst_mkfs ${LTP_DEV_FS_TYPE} ${LTP_DEV}
return
fi
Thanks
Shuang
next reply other threads:[~2015-12-25 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 17:37 Shuang Qiu [this message]
2016-01-05 13:48 ` [LTP] mkfs01 testcases issue Cyril Hrubis
2016-01-05 14:21 ` Cyril Hrubis
2016-01-05 14:35 ` Cyril Hrubis
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=567D7ED0.2060706@oracle.com \
--to=shuang.qiu@oracle.com \
--cc=ltp@lists.linux.it \
/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