From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free?
Date: Tue, 17 Oct 2017 23:19:54 +0000 (UTC) [thread overview]
Message-ID: <pan$7012a$2aa3b3f4$9c2bb50d$e909647e@cox.net> (raw)
In-Reply-To: 5de6f85d-ddff-8448-ebc3-54df455c4961@gmail.com
Vladimir Panteleev posted on Tue, 17 Oct 2017 17:19:45 +0000 as excerpted:
> I'm experiencing some issues with a btrfs filesystem - mounting and
> other operations taking forever, a balance that takes hours to start and
> never completes (due to the error in the subject line), and I've also
> seen the NULL pointer dereference in free_reloc_roots which Naohiro Aota
> fixed in 4.13.5 (I was on 4.13.4 at the time).
You may be running into the huge-over-allocation bug in recent kernels.
There's a fix that should be in 4.14 that I'd have thought would be
backported to stable kernels by now, but perhaps not.
So your options are:
* try the balance on 4.14-rc5+, where the known bug should be fixed
* wait for 4.14 release and try the balance there
* wait for the backport to stable
* revert to an earlier kernel, say the latest 4.9-LTS series kernel, and
try it there (tho I'm not sure if the bug had appeared yet on 4.9 or not,
if it had, then it's as unlikely to be fixed there as in 4.13 current)
If you still see the bug on 4.14-rc5+, then you're likely running into
some other bug that has similar effects, as to the best of my knowledge
as a btrfs user following the list, it's fixed there.
Reverting to the long-in-the-tooth-for-btrfs 4.4 LTS series should be
before that bug appeared for sure, and in theory, being an LTS, it should
have critical bug fixes since then, but I really hate to recommend it as
a lot really has happened in btrfs since then. Here, I'm actually
running 4.14-rc5 (and ran 14 series from rc3 or so), tho I tend to far
smaller partitioned btrfs and haven't run into that particular problem,
but I'd obviously prefer 4.14-rc5 to the long-in-the-tooth-even-if-LTS
4.4. YMMV.
And of course your last option is to wait for a developer or regular more
closely following that particular bug and the patch fixing it to tell you
whether it's in 4.13.6 or not, and thus whether you're still affected by
it, or that it must be something else with similar symptoms. But lacking
definitive word from them... well I'd obviously try 4.14-rc5+, since I'm
already running 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-10-17 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:19 4.13: "error in btrfs_run_delayed_refs:3009: errno=-28 No space left" with 1.3TB unallocated / 737G free? Vladimir Panteleev
2017-10-17 23:19 ` Duncan [this message]
2017-10-19 8:16 ` Vladimir Panteleev
2017-10-19 12:14 ` Martin Raiber
2017-10-22 15:08 ` Vladimir Panteleev
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$7012a$2aa3b3f4$9c2bb50d$e909647e@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).