From: Chen Rong <rongx.a.chen@intel.com>
To: fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: philip.li@intel.com, rongx.a.chen@intel.comrongx.a.chen@intel.com
Subject: xfstests: generic/342 run failed in f2fs
Date: Mon, 25 Dec 2017 13:28:16 +0800 [thread overview]
Message-ID: <2d524305-ecb5-8600-a92a-d79b717b8d13@intel.com> (raw)
Hi, everyone:
the issue as below:
# ./check generic/342
FSTYP -- f2fs
PLATFORM -- Linux/x86_64 node01 4.15.0-rc4
MKFS_OPTIONS -- /dev/sde1
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sde1 /tmp/test1
generic/342 - output mismatch (see
/home/ubuntu/git/xfstests-dev/results//generic/342.out.bad)
--- tests/generic/342.out 2017-12-13 13:47:20.144000000 -0500
+++ /home/ubuntu/git/xfstests-dev/results//generic/342.out.bad
2017-12-25 11:13:12.928000000 -0500
@@ -8,8 +8,7 @@
48c940ba3b8671d3d6ea74e4ccad8ca3 SCRATCH_MNT/a/bar
Directory a/ contents after log replay:
SCRATCH_MNT/a:
-bar
foo
File digests after log replay:
9e5d56a1f9b2c93589f9d55480f971a1 SCRATCH_MNT/a/foo
...
(Run 'diff -u tests/generic/342.out
/home/ubuntu/git/xfstests-dev/results//generic/342.out.bad' to see the
entire diff)
Ran: generic/342
Failures: generic/342
Failed 1 of 1 tests
Is it a problem with my computer or a already known issue with f2fs?
thanks!
next reply other threads:[~2017-12-25 5:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 5:28 Chen Rong [this message]
2017-12-25 5:56 ` xfstests: generic/342 run failed in f2fs Eric Sandeen
2017-12-25 6:30 ` Chen Rong
2017-12-25 7:47 ` Eric Sandeen
2017-12-25 16:31 ` Theodore Ts'o
2017-12-27 19:11 ` Jaegeuk Kim
2017-12-28 3:17 ` Chao Yu
2017-12-28 3:41 ` Theodore Ts'o
2017-12-28 9:09 ` Dave Chinner
2017-12-28 16:29 ` Jaegeuk Kim
2017-12-28 16:59 ` Eric Sandeen
2017-12-28 21:21 ` Dave Chinner
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=2d524305-ecb5-8600-a92a-d79b717b8d13@intel.com \
--to=rongx.a.chen@intel.com \
--cc=fstests@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=philip.li@intel.com \
--cc=rongx.a.chen@intel.comrongx.a.chen \
/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;
as well as URLs for NNTP newsgroup(s).