All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: ERROR: scrubbing <dev> failed for device id 1: ret=-1, errno=28 (No space left on device)
Date: Fri, 18 Dec 2015 21:38:04 +0100	[thread overview]
Message-ID: <1450469988@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <CAPmG0jZYidy-ra-R-C5GQNQhUZeVSB6anCg7N9sFSY5NrrO61w@mail.gmail.com>

Henk Slager wrote...

> you need to do some balancing, as I think that the free space is too
> fragmented and the system fails to allocate extra metadata space
> needed for scrub doing writes into metadata.
> 
> # btrfs balance start -dusage=<number>
> with number somewhere between 5 and 50; first start with lower number
> and repeat and increase until the 5.17GiB gets closer down to the
> 3.75GiB

Thanks, that one worked with number 100. Still some ENOSPC errors but
appeareantly good enough to make scrubbing work.

> The issue is that for for a filesystem of this size (6.5GiB), it would
> have been better to have mixed data/metadata allocation. See help of
> mkfs.btrfs. So maybe you want to recreate the fs like that, otherwise
> you might easily hit this problem again if you don't monitor free
> space / balance regularly.

Will keep that in mind. Just out of curiousity: Initially, the file
system size was just 4 Gibyte. Is it possible this made things worse?


Oh, and by the way:

--- a/Documentation/mkfs.btrfs.asciidoc
+++ b/Documentation/mkfs.btrfs.asciidoc
@@ -77,7 +77,7 @@ where the space is reserved for the other block group type, is not available for
 allocation and can lead to ENOSPC state.
 +
 The recommended size for the mixed mode is for filesystems less than 1GiB. The
-soft recommendation is to use it for filesystems smaller than 5GiB. Thie mixed
+soft recommendation is to use it for filesystems smaller than 5GiB. The mixed
 mode may lead to degraded performance on larger filesystems, but is otherwise
 usable, even on multiple devices.
 +


    Christoph

  reply	other threads:[~2015-12-18 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  7:28 ERROR: scrubbing <dev> failed for device id 1: ret=-1, errno=28 (No space left on device) Christoph Biedl
2015-12-18 12:08 ` Henk Slager
2015-12-18 20:38   ` Christoph Biedl [this message]
2015-12-19 15:31     ` Henk Slager

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=1450469988@msgid.manchmal.in-ulm.de \
    --to=linux-kernel.bfrz@manchmal.in-ulm.de \
    --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.