Hey Alice, Thanks again for putting together the patches.
Unfortunately, testing the patched kernel on zephir resulted in a kernel panic during boot, before I could run TRIM. Things got considerably worse afterward. Even the previous kernel could no longer boot because the root XFS filesystem had an inconsistent journal. I had to boot from a live USB, recover the LVM RAID arrays, and repair XFS using `xfs_repair -L`. The server is finally back up on `7.0.0-38-generic`, and I've verified that the storage devices appear healthy. I wasn't able to capture the initial panic trace, and I can't say for certain whether the XFS corruption was caused by the patched kernel. However, given the amount of recovery work and the risk of data loss, I'm not comfortable attempting another test on either of my servers. I'm happy to share any of the logs and diagnostic information I've already collected, but I'd prefer not to risk another filesystem recovery. Thanks for understanding! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169515 Title: # fstrim triggers IRQ stack overflow in device-mapper completion on LVM RAID1 (7.0.0-34-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169515/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
