https://bugzilla.kernel.org/show_bug.cgi?id=193661 Christian Kujau (lists@xxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lists@xxxxxxxxxxxxxxx --- Comment #9 from Christian Kujau (lists@xxxxxxxxxxxxxxx) --- 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.
