linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Panteleev <thecybershadow@gmail.com>
To: Martin Raiber <martin@urbackup.org>,
	1i5t5.duncan@cox.net, 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: Sun, 22 Oct 2017 15:08:14 +0000	[thread overview]
Message-ID: <7ab8dd62-aaaa-b112-6643-6311290db03e@gmail.com> (raw)
In-Reply-To: <0102015f348e9867-37a2530c-b78e-4efb-9528-d13136194eae-000000@eu-west-1.amazonses.com>

On 2017-10-19 12:14, Martin Raiber wrote:
> You could also mount with
> "enospc_debug" to give the devs more infos about this issue.
> I am having more ENOSPC issues with 4.9.x than with the latest 4.14.

Here is the dmesg output with -o enospc_debug, hopefully it will be 
useful for someone:
https://dump.thecybershadow.net/266ad878bed7921ccca3a7f624df0cc7/scratch.txt

> for me a work-around for something like this has been to reduce the
> amount of dirty memory

In the end I deleted some snapshots, that seemed to free up enough 
metadata for the balance to continue. After 25 hours, a balance with 
-dusage=10 finished and freed up 344GB of "Device unallocated" space.

-- 
Best regards,
  Vladimir

      reply	other threads:[~2017-10-22 15:08 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
2017-10-19  8:16   ` Vladimir Panteleev
2017-10-19 12:14     ` Martin Raiber
2017-10-22 15:08       ` Vladimir Panteleev [this message]

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=7ab8dd62-aaaa-b112-6643-6311290db03e@gmail.com \
    --to=thecybershadow@gmail.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@urbackup.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).