On Thu, Jul 5, 2018 at 9:35 AM Colin Ian King <[email protected]> wrote: > > What is the stress-ng command that is being run by /usr/lib/plainbox- > provider-checkbox/bin/disk_stress_ng - without knowing that it's hard to > figure out the initial stressor conditions
It runs several stress-ng tests against the target. In my reproduction, I've disabled all but one, and that is 'chdir'. Here's the invocation: stress-ng --aggressive --verify --timeout 240 --aio 0 --hdd-opts dsync --readahead-bytes 16M -k This is the only stress-ng command that runs after boot/fresh-mkfs. However, as I mentioned, this stress-ng command alone did not appear to trigger the issue. I suspect that this is due to sysctls that cert sets before the running the test, but I have not attempted to prove that yet. -dann -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780137 Title: [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780137/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
