linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jorge Bastos <jorge.mrbastos@gmail.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: Christoph Anton Mitterer <calestyo@scientia.org>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: ENOSPC while df shows 826.93GiB free
Date: Tue, 7 Dec 2021 15:10:07 +0000	[thread overview]
Message-ID: <CAHzMYBRf63mcgVHiO-8o2UFffjB7Y+7FiOdnWRRb7RzfOBhi5Q@mail.gmail.com> (raw)
In-Reply-To: <20211207072128.GL17148@hungrycats.org>

Hi,

Disregard my last email, it is the same issue of metadata exhaustion,
just didn't understand why two identical file systems used in the same
way in the same server behaved so differently, if I convert metadata
from raid1 to single it will leave some extra metadata chunks and I
was then able to fill up the data chunks, of course now I can't
balance metadata to raid1 again, I wish there was an easy way to
allocate an extra metadata chunk when there's available space.

Regards,
Jorge Bastos

  parent reply	other threads:[~2021-12-07 15:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  2:29 ENOSPC while df shows 826.93GiB free Christoph Anton Mitterer
2021-12-07  2:59 ` Qu Wenruo
2021-12-07  3:06   ` Christoph Anton Mitterer
2021-12-07  3:29     ` Qu Wenruo
2021-12-07  3:44       ` Christoph Anton Mitterer
2021-12-07  4:56         ` Qu Wenruo
2021-12-07 14:30           ` Christoph Anton Mitterer
2021-12-07  7:21         ` Zygo Blaxell
2021-12-07 12:31           ` Jorge Bastos
2021-12-07 15:07           ` Christoph Anton Mitterer
2021-12-07 18:14             ` Zygo Blaxell
2021-12-16 23:16               ` Christoph Anton Mitterer
2021-12-17  2:00                 ` Qu Wenruo
2021-12-17  3:10                   ` Christoph Anton Mitterer
2021-12-17  5:53                 ` Zygo Blaxell
2021-12-07 15:10           ` Jorge Bastos [this message]
2021-12-07 15:22             ` Christoph Anton Mitterer
2021-12-07 16:11               ` Jorge Bastos
2021-12-07 15:39 ` Phillip Susi
2021-12-16  3:47   ` Christoph Anton Mitterer

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=CAHzMYBRf63mcgVHiO-8o2UFffjB7Y+7FiOdnWRRb7RzfOBhi5Q@mail.gmail.com \
    --to=jorge.mrbastos@gmail.com \
    --cc=calestyo@scientia.org \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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).