From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: fix fsync failure with SQL Server workload
Date: Mon, 24 May 2021 11:35:52 +0100 [thread overview]
Message-ID: <cover.1621851896.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This patchset fixes a fsync failure (-EIO) and transaction abort during
a workload for Microsoft's SQL Server running in a Docker container as
reported at:
https://lore.kernel.org/linux-btrfs/93c4600e-5263-5cba-adf0-6f47526e7561@in.tum.de/
It also adds an optimization for the workload, by removing lots of fsyncs
that trigger the slow code path and replacing them with ones that use the
fast path, reducing the workload's runtime by about -12% on my test box.
Filipe Manana (3):
btrfs: fix fsync failure and transaction abort after writes to
prealloc extents
btrfs: fix misleading and incomplete comment of btrfs_truncate()
btrfs: don't set the full sync flag when truncation does not touch
extents
fs/btrfs/ctree.h | 2 +-
fs/btrfs/file-item.c | 98 ++++++++++++++++++++++++++++---------
fs/btrfs/free-space-cache.c | 2 +-
fs/btrfs/inode.c | 65 +++++++++++++++++-------
fs/btrfs/tree-log.c | 5 +-
5 files changed, 128 insertions(+), 44 deletions(-)
--
2.28.0
next reply other threads:[~2021-05-24 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 10:35 fdmanana [this message]
2021-05-24 10:35 ` [PATCH 1/3] btrfs: fix fsync failure and transaction abort after writes to prealloc extents fdmanana
2021-05-24 10:35 ` [PATCH 2/3] btrfs: fix misleading and incomplete comment of btrfs_truncate() fdmanana
2021-05-24 10:35 ` [PATCH 3/3] btrfs: don't set the full sync flag when truncation does not touch extents fdmanana
2021-05-24 14:31 ` [PATCH 0/3] btrfs: fix fsync failure with SQL Server workload Anand Jain
2021-05-25 15:02 ` David Sterba
2021-05-25 15:20 ` Filipe Manana
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=cover.1621851896.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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.