From: Omar Sandoval <osandov@osandov.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Christian Theune <ct@flyingcircus.io>, linux-btrfs@vger.kernel.org
Subject: Re: Downgrading kernel 4.9 to 4.4 with space_cache=v2 enabled?
Date: Fri, 24 Feb 2017 10:35:58 -0800 [thread overview]
Message-ID: <20170224183558.GB27484@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <21390090-717d-2dff-35ec-86bcbab342ae@gmail.com>
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.
next prev parent reply other threads:[~2017-02-24 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:51 Downgrading kernel 4.9 to 4.4 with space_cache=v2 enabled? Christian Theune
2017-02-23 12:34 ` Austin S. Hemmelgarn
[not found] ` <71958378-5AB4-4E66-8F54-60215141D1BB@flyingcircus.io>
2017-02-23 13:19 ` Christian Theune
2017-02-23 13:38 ` Austin S. Hemmelgarn
2017-02-24 18:35 ` Omar Sandoval [this message]
2017-02-24 0:54 ` Qu Wenruo
2017-02-24 12:23 ` Austin S. Hemmelgarn
2017-02-24 18:34 ` Omar Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170224183558.GB27484@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=ahferroin7@gmail.com \
--cc=ct@flyingcircus.io \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox