All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Robertson <dan@dlrobertson.com>
To: linux-bcachefs@vger.kernel.org
Cc: Dan Robertson <dan@dlrobertson.com>,
	Kent Overstreet <kent.overstreet@gmail.com>
Subject: [PATCH 0/1] generic/103: increase reserved bytes for bcachefs
Date: Thu, 24 Jun 2021 22:11:17 -0400	[thread overview]
Message-ID: <20210625021118.28813-1-dan@dlrobertson.com> (raw)

After some testing it seems that generic/103 fails intermittently due to
a split leaf that can be hit in fallocate. Since the bcachefs node sizes
are larger on bcachefs than some other filesystems the reserved size
needs to be bumped up a bit when FSTYP is bcachefs.

On a system that generic/103 failed semi-regularly on, I can now it
in a loop without hitting a failure.

Dan Robertson (1):
  generic/103: increase reserved bytes for bcachefs

 tests/generic/103 | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)


             reply	other threads:[~2021-06-25  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  2:11 Dan Robertson [this message]
2021-06-25  2:11 ` [PATCH 1/1] generic/103: increase reserved bytes for bcachefs Dan Robertson
2021-06-25  3:05   ` Kent Overstreet

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=20210625021118.28813-1-dan@dlrobertson.com \
    --to=dan@dlrobertson.com \
    --cc=kent.overstreet@gmail.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 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.