Right, I think this occurs when ext4 goes read-only. A simple way to reproduce this on i386 systems with that kernel is:
sudo stress-ng --sockpair 10 && sudo stress-ng --xattr 10
xattr test causes ext4 to detect xattr issues and the file system gets remounted r/o, and we no longer can log the stress-ng ADT test log.
Right, I think this occurs when ext4 goes read-only. A simple way to reproduce this on i386 systems with that kernel is:
sudo stress-ng --sockpair 10 && sudo stress-ng --xattr 10
xattr test causes ext4 to detect xattr issues and the file system gets remounted r/o, and we no longer can log the stress-ng ADT test log.