linux-bcachefs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Dan Robertson <dan@dlrobertson.com>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: [PATCH 1/1] generic/103: increase reserved bytes for bcachefs
Date: Thu, 24 Jun 2021 23:05:00 -0400	[thread overview]
Message-ID: <YNVH3Cnw8bwYjJ1Y@moria.home.lan> (raw)
In-Reply-To: <20210625021118.28813-2-dan@dlrobertson.com>

On Thu, Jun 24, 2021 at 10:11:18PM -0400, Dan Robertson wrote:
> The bcachefs btree nodes are quite large. If we only reserve 512 bytes
> we hit an intermittent failure where the fallocate that is intented to
> fill the available space triggers a btree node split and the exente update
> is interrupted. The retry of the extent update will fail because the
> new amount of available space is less than that of the request.
> 
> Signed-off-by: Dan Robertson <dan@dlrobertson.com>

Thanks, merged

      reply	other threads:[~2021-06-25  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  2:11 [PATCH 0/1] generic/103: increase reserved bytes for bcachefs Dan Robertson
2021-06-25  2:11 ` [PATCH 1/1] " Dan Robertson
2021-06-25  3:05   ` Kent Overstreet [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=YNVH3Cnw8bwYjJ1Y@moria.home.lan \
    --to=kent.overstreet@gmail.com \
    --cc=dan@dlrobertson.com \
    --cc=linux-bcachefs@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).