From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 193661] xattr ext4_xattr_block_find, bad block on cleanly formatted ext4 partition
Date: Wed, 22 Feb 2017 00:24:33 +0000 [thread overview]
Message-ID: <bug-193661-13602-XFyzym7OFf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-193661-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=193661
Christian Kujau (lists@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #9 from Christian Kujau (lists@nerdbynature.de) ---
Wow, this triggers in a Debian/unstable 64-bit VM here after the first run:
$ mkfs.ext4 /dev/sdd
$ mount -t ext4 /dev/sdd /mnt/disk && cd /mnt/disk
$ time ~/193661.sh
++ seq 30
+ for i in $(seq 30)
+ /usr/local/sbin/stress-ng --xattr 8 -t 10
stress-ng: info: [2639] dispatching hogs: 8 xattr
stress-ng: info: [2639] cache allocate: default cache size: 6144K
stress-ng: fail: [2647] stress-ng-xattr: fsetxattr failed, errno=117
(Structure needs cleaning)
stress-ng: error: [2639] process 2647 (stress-ng-xattr) terminated with an
error, exit status=1
stress-ng: info: [2639] unsuccessful run completed in 10.01s
+ rc=2
+ '[' 2 -ne 0 ']'
+ exit 1
real 0m10.019s
user 0m1.460s
sys 0m26.752s
$ dmesg | tail -2
[ 494.311212] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts:
(null)
[ 550.828337] EXT4-fs error (device sdd): ext4_xattr_block_find:786: inode
#524292: comm stress-ng-xattr: bad block 2105384
$ uname -rv
4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-02-22 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:06 [Bug 193661] New: xattr ext4_xattr_block_find, bad block on cleanly formatted ext4 partition bugzilla-daemon
2017-01-30 16:08 ` [Bug 193661] " bugzilla-daemon
2017-01-30 16:10 ` bugzilla-daemon
2017-01-30 16:24 ` bugzilla-daemon
2017-01-30 16:48 ` bugzilla-daemon
2017-01-30 16:50 ` bugzilla-daemon
2017-01-30 16:53 ` bugzilla-daemon
2017-01-30 16:55 ` bugzilla-daemon
2017-02-21 14:52 ` bugzilla-daemon
2017-02-22 0:24 ` bugzilla-daemon [this message]
2017-02-28 14:01 ` bugzilla-daemon
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-193661-13602-XFyzym7OFf@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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