For us, fstrim was the frontend to the bug and running it consistently damaged our filesystems. That is why util-linux was chosen as the affected package. Also removing the cron file will not be sufficient as any update to the package (using cron-apt) might re-install it. Maybe a conflicting change would be a better choice. Still seems to brittle in light of such severe consequences. Mitigated by not upgrading to 16.04 for now.
Since the system concerned is not connected to the web, Apport as described here (https://wiki.ubuntu.com/Apport#Tools) will not work. Also, Ubuntu server did not install apport when selecting 'Basic Ubuntu Server' in the installer. If there is additional information that might be useful, let us know. Further response may be delayed due to people going on vacation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686687 Title: fstrim destroying XFS on SAN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
