From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201549] New: [xfstests xfs/019]: mkfs.xfs: warning - iflush_int failed (-117)
Date: Sun, 28 Oct 2018 14:20:52 +0000 [thread overview]
Message-ID: <bug-201549-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201549
Bug ID: 201549
Summary: [xfstests xfs/019]: mkfs.xfs: warning - iflush_int
failed (-117)
Product: File System
Version: 2.5
Kernel Version: v4.18
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: zlang@redhat.com
Regression: No
xfs/019 fails on s390x. mkfs.xfs always fails as below:
# mkfs.xfs -f -n version=2 -p /tmp/36771.proto /dev/loop1
meta-data=/dev/loop1 isize=512 agcount=4, agsize=786496 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=0
data = bsize=4096 blocks=3145984, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Metadata corruption detected at 0x101214a, inode 0x89 data fork
mkfs.xfs: warning - iflush_int failed (-117)
cache_purge: shake on cache 0x8e4be40 left 1 nodes!?
cache_purge: shake on cache 0x8e4be40 left 1 nodes!?
cache_purge: shake on cache 0x8e4be40 left 1 nodes!?
cache_zero_check: refcount is 1, not zero (node=0x8e76a60)
# cat /tmp/36771.proto
DUMMY1
0 0
: root directory
d--777 3 1
: a directory
directory d--755 3 1
file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_0 ---755 3 1 /tmp/36771.file
file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_1 ---755 3 1 /tmp/36771.file
file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_2 ---755 3 1 /tmp/36771.file
file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_3 ---755 3 1 /tmp/36771.file
file_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_4 ---755 3 1 /tmp/36771.file
$
: back in the root
setuid -u-666 0 0 /tmp/36771.file
setgid --g666 0 0 /tmp/36771.file
setugid -ug666 0 0 /tmp/36771.file
block_device b--012 3 1 161 162
char_device c--345 3 1 177 178
pipe p--670 0 0
symlink l--123 0 0 bigfile
: a file we actually read
bigfile ---666 3 0 /tmp/36771.file.2
: done
$
# cat /tmp/36711.file
fish
The file "/tmp/36771.file.2" is generated by:
# xfstests/src/devzero -b 2048 -n 2 -c -v 44 /tmp/36771.file.2
Version-Release number of selected component (if applicable):
# mkfs.xfs -V
mkfs.xfs version 4.19.0-rc0
kernel 4.18
How reproducible:
100%
Steps to Reproduce:
run xfs/019 on s390x
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2018-10-28 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-201549-201763@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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 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.