Comment 5 for bug 1780137

Revision history for this message
dann frazier (dannf) wrote :

The significant difference in the cert test wrapper actually appears to be that it creates a directory in which to run the test, vs. running it at the root of the mount point. I'm able to reproduce the failure outside of cert after a fresh reboot with the following script. The fs.aio-max-nr sysctl was a red herring.

mkdir -p /tmp/mnt
# My script does a mkfs.ext4 -F, but omitting that here in case someone blindly cut & pastes
mkfs.ext4 /dev/sda1
mount /dev/sda1 /tmp/mnt
# Running directly under /tmp/mnt doesn't trigger the issue, we need
# this subdirectory for some reason
mkdir -p /tmp/mnt/tmp/disk_stress_ng_f70f0f26-b332-4c48-9e07-67c529770e3d
stress-ng --aggressive --verify --timeout 240 --temp-path /tmp/mnt/tmp/disk_stress_ng_f70f0f26-b332-4c48-9e07-67c529770e3d --chdir 0 --hdd-opts dsync --readahead-bytes 16M -k

@Colin: I updated the description to note that we have seen this on 2 different HiSilicon servers that use different HiSilicon SoCs. We've also tested on a Cavium Sabre (ThunderX2-based) board, and were unable to reproduce it there.