From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: 4.4.0 - no space left with >1.7 TB free space left
Date: Fri, 8 Apr 2016 19:53:48 +0000 (UTC) [thread overview]
Message-ID: <pan$caab3$faaff583$6f85afa6$6f034ed9@cox.net> (raw)
In-Reply-To: 20160408165332.450659c4@natsu
Roman Mamedov posted on Fri, 08 Apr 2016 16:53:32 +0500 as excerpted:
> It's not in 4.4.6 either. I don't know why it doesn't get included, or
> what we need to do. Last time I asked, it was queued:
> http://www.spinics.net/lists/linux-btrfs/msg52478.html But maybe that
> meant 4.5 or 4.6 only? While the bug is affecting people on 4.4.x today.
Patches must make it to the current development kernel before they're
eligible for stable. Additionally, they need to be cced to stable as
well, in ordered to be queued there.
So check 4.5 and 4.6-rc. If it's in neither of those, it's not going to
be in stable yet. Once it's in the development kernel, see if it was cced
to stable and if needed, ask the author and btrfs devs to cc it to stable.
Tho sometimes stable can get a backlog as well. I know earlier this year
they were dealing with one, but I follow release or development, not
stable, and don't know what stable's current status is.
If it gets to stable, and it wasn't for a bug introduced /after/ 4.4, it
should eventually get into 4.4, as that's an LTS kernel. But it might
take awhile, as the above discussion hints.
--
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:[~2016-04-08 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:22 4.4.0 - no space left with >1.7 TB free space left Tomasz Chmielewski
2016-02-08 11:24 ` Roman Mamedov
2016-02-08 12:15 ` Tomasz Chmielewski
2016-02-08 12:17 ` Roman Mamedov
2016-04-08 11:36 ` Tomasz Chmielewski
2016-04-08 11:53 ` Roman Mamedov
2016-04-08 13:20 ` Tomasz Chmielewski
2016-04-08 19:53 ` Duncan [this message]
2016-05-12 6:03 ` Tomasz Chmielewski
2016-05-12 6:07 ` Tomasz Chmielewski
2016-09-15 8:02 ` Roman Mamedov
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$caab3$faaff583$6f85afa6$6f034ed9@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;
as well as URLs for NNTP newsgroup(s).