All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Russell Coker <russell@coker.com.au>, linux-btrfs@vger.kernel.org
Subject: Re: 3.16.0 Debian kernel hang
Date: Fri, 4 Dec 2015 08:08:58 -0500	[thread overview]
Message-ID: <5661906A.50309@gmail.com> (raw)
In-Reply-To: <201512042100.58127.russell@coker.com.au>

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

On 2015-12-04 05:00, Russell Coker wrote:
> One of my test laptops started hanging on mounting the root filesystem.  I
> think that it had experience an unexpected power outage prior to that which
> may have caused corruption.
>
> When I tried to mount the root filesystem the mount process would stick in D
> state, there would be no disk IO, and the computer would get hot - presumably
> due to kernel CPU use even though "top" didn't seem to indicate that.
>
> When I mounted the filesystem with a 4.2.0 kernel it said "The free space cache
> file (1103101952) is invalid, skip it" and then things worked.  Now that the
> machine is running 4.2.0 everything is fine.
>
> I know that there are no plans to backport things to 3.16 and I don't think
> the Debian people are going to be very interested in this.  So this message is
> a FYI for users, maybe consider not using the Debian/Jessie kernel for BTRFS
> systems.
>
I'd suggest extending that suggestion to:
If you're not using an Enterprise distro (RHEL, SLES, CentOS, OEL), then 
you should probably be building your own kernel, ideally using upstream 
sources.

Ubuntu is notorious for picking 'stable' kernels that then fail to be 
marked by kernel.org as LTS, Debian picks kernels that are multiple 
versions old by the time they make a release, and I've heard similar 
from other non-enterprise distros that don't inherently make you build 
your own kernel.  Even among ones that you have to build the kernel 
yourself anyway, there are issues (Gentoo for example doesn't often mark 
new kernels as stable, even when they are perfectly usable for pretty 
much everyone).


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-12-04 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 10:00 3.16.0 Debian kernel hang Russell Coker
2015-12-04 13:08 ` Austin S Hemmelgarn [this message]
2015-12-04 13:42   ` Russell Coker
2015-12-04 13:53     ` Austin S Hemmelgarn
2015-12-04 14:26       ` Russell Coker
2015-12-04 16:13         ` Austin S Hemmelgarn
2015-12-05 12:44   ` Duncan

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=5661906A.50309@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.