From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel hangs during balance
Date: Thu, 21 Dec 2017 06:26:16 +0000 (UTC) [thread overview]
Message-ID: <pan$678dc$737b7f30$15572b76$e6022b@cox.net> (raw)
In-Reply-To: 09697eee-b6f6-eb02-1c0d-1d6f156985f9@applied-asynchrony.com
Holger Hoffstätte posted on Wed, 20 Dec 2017 20:58:14 +0100 as excerpted:
> On 12/20/17 20:02, Chris Murphy wrote:
>> I don't know if it's the sending MUA or the list server, but the line
>> wrapping makes this much harder to follow. I suggest putting it in a
>> text file and attaching the text file. It's definitely not on the
>> receiving side, I see it here also:
>> https://www.spinics.net/lists/linux-btrfs/msg72872.html
>
> You can see enough to suggest that blk-mq is hanging, which is
> "unsurprising" (being kind here) with such an old kernel. Rich, build
> your kernel with CONFIG_SCSI_MQ_DEFAULT=n or boot with
> scsi_mod.use_blk_mq=n as kernel prarameter.
Well, the kernel is 4.4 "el repo". 4.4 /is/ an LTS (and elrepo is AFAIK
a red hat backports repo, not sure how official, but useful for people on
red hat), but it's now the second-back LTS, with 4.9 and the new 4.14
being newer LTS series.
The thing is that this is the btrfs list, and we're development and thus
rather forward focused here. As such, we normally want at /least/ the
second newest (first back) lts series kernel for best chance at
reasonable support. While I understand people who want to stick with LTS
being reluctant to go with the /newest/ LTS before even a single current
release has passed, making that LTS still a bit new as such things go,
certainly the one-back LTS, 4.9, should be reasonable.
So yes, tho 4.4 is at least an LTS, for purposes of btrfs and this list,
it really is rather old now, and an upgrade, presumably to 4.9 in keeping
with the LTS theme, would be recommended. If the issue can be confirmed
on the current and LTS 4.14, so much the better, but certainly, 4.9 is a
recommended upgrade, and a bug there would still be in the concern for a
fix range, while 4.4... really is just out of the focus range for this
list, tho various longer focus distros will of course still provide
support for it.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-12-21 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 16:09 kernel hangs during balance Rich Rauenzahn
2017-12-19 17:08 ` Rich Rauenzahn
2017-12-19 17:14 ` Hans van Kranenburg
2017-12-19 17:48 ` Rich Rauenzahn
2017-12-20 16:24 ` Rich Rauenzahn
2017-12-20 19:02 ` Chris Murphy
2017-12-20 19:58 ` Holger Hoffstätte
2017-12-20 21:11 ` Rich Rauenzahn
2017-12-21 6:26 ` Duncan [this message]
2017-12-23 19:59 ` Rich Rauenzahn
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='pan$678dc$737b7f30$15572b76$e6022b@cox.net' \
--to=1i5t5.duncan@cox.net \
--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