All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] ENOSPC refinements
Date: Wed, 10 Apr 2019 15:56:08 -0400	[thread overview]
Message-ID: <20190410195610.84110-1-josef@toxicpanda.com> (raw)

I noticed our continuous testing for btrfs started timing out recently, and dug
down to discover that generic/224 was taking upwards of an hour to run.  This
test should take seconds to run, so this is a problem.

Fix this by reworking how we do delalloc metadata reservations, as described in
patch 2/2.

I also noticed we don't quite do the right thing when we are mostly O_DIRECT,
and addressed this in patch 1/2.  I've run these through xfstests and everything
is back to normal.  Thanks,

Josef

             reply	other threads:[~2019-04-10 19:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 19:56 Josef Bacik [this message]
2019-04-10 19:56 ` [PATCH 1/2] btrfs: track odirect bytes in flight Josef Bacik
2019-04-12 10:17   ` Nikolay Borisov
2019-04-12 13:30     ` Josef Bacik
2019-04-24 17:26     ` David Sterba
2019-04-10 19:56 ` [PATCH 2/2] btrfs: reserve delalloc metadata differently Josef Bacik
2019-04-12 13:06   ` Nikolay Borisov
2019-04-12 13:26     ` Josef Bacik
2019-04-12 13:35       ` Nikolay Borisov
2019-04-12 13:37         ` Josef Bacik
2019-04-29 18:33   ` David Sterba
2019-04-25 15:22 ` [PATCH 0/2] ENOSPC refinements David Sterba
2019-04-25 20:52 ` [PATCH][v2] btrfs: track odirect bytes in flight Josef Bacik
2019-04-29 18:17   ` David Sterba

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=20190410195610.84110-1-josef@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --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.