Kernel release bisection: cosmic: 4.18.0-26: incremental, dry-run: panic about 303GB cosmic: 4.18.0-26: incremental, dry-run: panic about 21GB cosmic: 4.18.0-26: incremental, dry-run: panic about 22GB
disco: 4.19.0-13: incremental, dry-run: testing: success The first run using 4.18.0-26 that was able to get to 303GB before panic is intriguing (it's why I ran it twice). All previous panics when doing an incremental rsync were ~20-22GB in (ala the subsequent two runs). The only thing we can say with certainty is the problem did not reproduce using 4.19.0-13. If the problem is a stack overflow then any changes in stack size, or different paths which use less stack, would result in the problem being less visible using the amount of data I'm copying (~1.4TB). ** Attachment added: "crash files from weekend of 10/3/20" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5417903/+files/crash_201003.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
