I'm personally not an xfs expert, but let me leave those two comments: - The test was unfortunately done on an old and outdated kernel from 16.04.1: 4.4.0-36 which got already replaced by several newer kernels Today we are already on level: 4.4.0.127.133 (and an even newer one is in the 'pipe' - in proposed: 4.4.0.128.134) $ rmadison --arch=ppc64el linux-generic | grep xenial linux-generic | 4.4.0.21.22 | xenial | ppc64el linux-generic | 4.4.0.127.133 | xenial-security | ppc64el linux-generic | 4.4.0.127.133 | xenial-updates | ppc64el linux-generic | 4.4.0.128.134 | xenial-proposed | ppc64el So please always update the kernel to the latest version from <ubuntu-release>-updates (or even proposed) before running such kinds of tests. Just make sure you have access to the updates (Ubuntu archive mirror) and do (something like): sudo apt update && sudo apt full-upgrade && sudo apt autoremove (and in case a kernel update was installed, reboot to activate it) So please re-run this test on the latest 4.4.0 version (today either 4.4.0.127.133 or even 4.4.0.128.134 from proposed.) - Does this problem also happen with the (latest) upstream 4.4 kernel? Knowing this would help to narrow down the issue.
** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775527 Title: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1775527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs