On Thu, Feb 23, 2017 at 08:38:02AM -0500, Austin S. Hemmelgarn wrote: > On 2017-02-23 08:19, Christian Theune wrote: > > Hi, > > > > just for future reference if someone finds this thread: there is a bit of > > output I’m seeing with this crashing kernel (unclear whether related to > > btrfs or not): > > > > 31 | 02/23/2017 | 09:51:22 | OS Stop/Shutdown #0x4f | Run-time critical > > stop | Asserted > > 32 | Linux kernel panic: Out of memo > > 33 | Linux kernel panic: ry and no k > > 34 | Linux kernel panic: illable pro > > 35 | Linux kernel panic: cesses... > > > OK, an OOM condition is (probably) not BTRFS related FWIW. IIRC, there were > a couple of issues with the OOM killer in 4.9, but I don't remember > specifics. To be able to determine anything useful though, you'd need a lot > more context in the kernel logs than just that.
Yeah, if there is a problem with the free space tree, I'd be happy to take a look, but it's impossible to tell from this. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
