linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Greed Rong <greedrong@gmail.com>
Cc: dsterba@suse.cz, Qu Wenruo <quwenruo.btrfs@gmx.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: BTRFS: Transaction aborted (error -24)
Date: Thu, 18 Jun 2020 14:34:18 +0200	[thread overview]
Message-ID: <20200618123418.GV27795@twin.jikos.cz> (raw)
In-Reply-To: <CA+UqX+PxF=prEHeS_u_K2ncT1MGqdmFsQeVTkDYLS6PqhJ7ddQ@mail.gmail.com>

On Mon, Jun 15, 2020 at 08:50:28PM +0800, Greed Rong wrote:
> Does that mean about 2^20 subvolumes can be created in one root btrfs?

No, subvolume ids are assigned incrementally, the amount is 2^64 so this
shouldn't be a problem in practice.

> The snapshot delete service was stopped a few weeks ago. I think this
> is the reason why the id pool is exhausted.
> I will try to run it again and see if it works.

The patches to reclaim the anon bdevs faster is small enough to be
pushed to older stable kernels, so you should be able to use it
eventually.

As a workaround, you can still delete the old subvolumes to get the
space back but perhaps at a slower rate and wait until the deleted
subvolumes are cleaned. That there's no way to get the number of used
anon bdevs makes it harder unfortunatelly.

  parent reply	other threads:[~2020-06-18 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 10:29 BTRFS: Transaction aborted (error -24) Greed Rong
2020-06-11 11:20 ` David Sterba
2020-06-11 12:37   ` Qu Wenruo
2020-06-11 13:52     ` David Sterba
2020-06-12  3:15       ` Greed Rong
2020-06-12  6:41         ` Qu Wenruo
2020-06-12 17:13         ` David Sterba
2020-06-15 12:50           ` Greed Rong
2020-06-16  0:38             ` Qu Wenruo
2020-06-18 12:34             ` David Sterba [this message]
2020-06-19  4:04               ` Greed Rong
2020-06-19  4:41                 ` Qu Wenruo
2020-06-12  5:38       ` Qu Wenruo

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=20200618123418.GV27795@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=greedrong@gmail.com \
    --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).