From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: David Sterba <dsterba@suse.com>
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: zoned: fix writes on a compressed zoned filesystem
Date: Wed, 12 May 2021 23:01:38 +0900 [thread overview]
Message-ID: <cover.1620824721.git.johannes.thumshirn@wdc.com> (raw)
David reported that I/O errors get thrown on a zoned filesystem with
compression enabled.
This happens because we're using regular writes instead of zoned append, but
with regular writes and increased parallelism, we cannot guarantee the data
placement requirements can be met.
This series switches the compressed I/O submission path to zone append writing
on a zoned filesystem.
Johannes Thumshirn (2):
btrfs: zoned: pass start block to btrfs_use_zone_append
btrfs: zoned: fix compressed writes
fs/btrfs/compression.c | 44 ++++++++++++++++++++++++++++++++++++++----
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/inode.c | 2 +-
fs/btrfs/zoned.c | 4 ++--
fs/btrfs/zoned.h | 5 ++---
5 files changed, 46 insertions(+), 11 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-12 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 14:01 Johannes Thumshirn [this message]
2021-05-12 14:01 ` [PATCH 1/2] btrfs: zoned: pass start block to btrfs_use_zone_append Johannes Thumshirn
2021-05-12 14:01 ` [PATCH 2/2] btrfs: zoned: fix compressed writes Johannes Thumshirn
2021-05-12 14:42 ` David Sterba
2021-05-17 7:07 ` Johannes Thumshirn
2021-05-17 9:12 ` David Sterba
2021-05-17 9:20 ` Johannes Thumshirn
2021-05-17 11:21 ` Johannes Thumshirn
2021-05-17 11:39 ` 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=cover.1620824721.git.johannes.thumshirn@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=dsterba@suse.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.