From: Roman Mamedov <rm@romanrm.net>
To: linux-btrfs.tebulin@xoxy.net
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left?
Date: Thu, 19 Nov 2015 10:58:30 +0500 [thread overview]
Message-ID: <20151119105830.48b57273@natsu> (raw)
In-Reply-To: <564CC90F.3060703@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On Wed, 18 Nov 2015 19:53:03 +0100
linux-btrfs.tebulin@xoxy.net wrote:
> $ uname -a
> Linux neptun 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8
> 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
For whatever unknown reason, Ubuntu repeatedly chooses to stabilize on exactly
the wrong kernel versions. Their recent releases were based on kernels 3.11,
3.13 and 3.19. None of these were chosen by the upstream as the "longterm"
branches, and as you can see none are listed anymore on https://www.kernel.org/
To emphasize -- the mainline Linux kernel developers (and Btrfs developers)
basically do not care anymore about 3.19 at all. What you currently use, is a
piecemeal of unknown quality, cobbled together by Ubuntu developers from
patches lifted either from 3.18 or 4.1 series -- by taking fixes they deem
important and frankensteining them together until they somehow seem to apply.
And do they back/forward-port Btrfs-related bugfixes?... all of them?... are
they doing that well enough? Just nobody knows.
So my suggestion would be to try a newer kernel from www.kernel.org: if the
problem disappears at 4.1 then just keep on using that, or 4.3 if you have to,
but otherwise that one might be a bit too new to start using right away.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-11-19 5:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:53 Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left? linux-btrfs.tebulin
2015-11-18 19:08 ` Hugo Mills
2015-11-19 0:42 ` Qu Wenruo
2015-11-19 2:16 ` Duncan
2015-11-20 11:39 ` Dmitry Katsubo
2015-11-20 13:21 ` Austin S Hemmelgarn
2015-11-20 13:27 ` Hugo Mills
2015-11-20 13:52 ` Austin S Hemmelgarn
2015-11-20 16:39 ` Dmitry Katsubo
2015-11-19 17:35 ` linux-btrfs.tebulin
2015-11-19 18:28 ` Hugo Mills
2015-11-19 18:45 ` linux-btrfs.tebulin
2015-11-19 18:56 ` linux-btrfs.tebulin
2015-11-19 19:26 ` linux-btrfs.tebulin
2015-11-20 3:14 ` Duncan
2015-11-20 9:38 ` linux-btrfs.tebulin
2015-11-20 10:44 ` Duncan
2015-11-20 14:25 ` Dmitry Katsubo
2015-11-19 20:18 ` Austin S Hemmelgarn
2015-11-19 5:58 ` Roman Mamedov [this message]
2015-11-19 8:31 ` Patrik Lundquist
2015-11-19 12:28 ` Austin S Hemmelgarn
2015-11-20 2:11 ` Duncan
2015-11-20 13:13 ` Austin S Hemmelgarn
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=20151119105830.48b57273@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs.tebulin@xoxy.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 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.