From: Johannes Thumshirn <jth@kernel.org>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v4 0/7] btrfs: rst: updates for RAID stripe tree
Date: Fri, 05 Jul 2024 17:13:46 +0200 [thread overview]
Message-ID: <20240705-b4-rst-updates-v4-0-f3eed3f2cfad@kernel.org> (raw)
Patch 1 replaces stripe extents in case we hit a EEXIST when inserting a
stripe extent on a write. This can happen i.e. on device-replace.
Patch 2 splits a stripe extent on partial delete of a stripe.
Patch 3 adds selftests for the stripe-tree delete code, these selftests
can and will be extended to cover insert and get as well.
Patch 4 fixes a deadlock between scrub and device replace when RST is
used.
Patch 5 get's rid of the pointless tree dump in case we're not finding an
RST entry.
Patch 6 is a prep-patch form #7 and renames btrfs_io_stripe::is_scrub to
commit_root.
Patch 7 changes the read code so we're looking at the commit_root for
relocation as well.
---
Changes in v4:
- Addressed Josef's comments
- Added patches 6 & 7
- Link to v3: https://lore.kernel.org/r/20240701-b4-rst-updates-v3-0-e0437e1e04a6@kernel.org
Changes in v3:
- Drop on-disk format change as it's in for-next
- Add patches 4 & 5
- Link to v2: https://lore.kernel.org/r/20240619-b4-rst-updates-v2-0-89c34d0d5298@kernel.org
Changes in v2:
- Added selftests for delete code
- Link to v1: https://lore.kernel.org/r/20240610-b4-rst-updates-v1-0-179c1eec08f2@kernel.org
---
Johannes Thumshirn (7):
btrfs: replace stripe extents
btrfs: rst: don't print tree dump in case lookup fails
btrfs: split RAID stripes on deletion
btrfs: stripe-tree: add selftests
btrfs: don't hold dev_replace rwsem over whole of btrfs_map_block
btrfs: rename brtfs_io_stripe::is_scrub to commit_root
btrfs: stripe-tree: also look at commit root on relocation
fs/btrfs/Makefile | 3 +-
fs/btrfs/bio.c | 3 +-
fs/btrfs/ctree.c | 1 +
fs/btrfs/raid-stripe-tree.c | 145 +++++++++++---
fs/btrfs/raid-stripe-tree.h | 5 +
fs/btrfs/scrub.c | 2 +-
fs/btrfs/tests/btrfs-tests.c | 3 +
fs/btrfs/tests/btrfs-tests.h | 1 +
fs/btrfs/tests/raid-stripe-tree-tests.c | 322 ++++++++++++++++++++++++++++++++
fs/btrfs/volumes.c | 28 +--
fs/btrfs/volumes.h | 2 +-
11 files changed, 470 insertions(+), 45 deletions(-)
---
base-commit: 3caaac6559396d9e668deb10345b7f3bb45f6ba9
change-id: 20240610-b4-rst-updates-d0aa696b9d5a
Best regards,
--
Johannes Thumshirn <jth@kernel.org>
next reply other threads:[~2024-07-05 15:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 15:13 Johannes Thumshirn [this message]
2024-07-05 15:13 ` [PATCH v4 1/7] btrfs: replace stripe extents Johannes Thumshirn
2024-07-05 23:19 ` Qu Wenruo
2024-07-08 11:43 ` Johannes Thumshirn
2024-07-08 22:14 ` Qu Wenruo
2024-07-09 5:49 ` Johannes Thumshirn
2024-07-09 5:36 ` Qu Wenruo
2024-07-05 15:13 ` [PATCH v4 2/7] btrfs: rst: don't print tree dump in case lookup fails Johannes Thumshirn
2024-07-05 23:20 ` Qu Wenruo
2024-07-05 15:13 ` [PATCH v4 3/7] btrfs: split RAID stripes on deletion Johannes Thumshirn
2024-07-05 23:26 ` Qu Wenruo
2024-07-08 4:56 ` Johannes Thumshirn
2024-07-08 5:20 ` Qu Wenruo
2024-07-08 5:25 ` Johannes Thumshirn
2024-07-08 10:52 ` Johannes Thumshirn
2024-07-08 23:02 ` Qu Wenruo
2024-07-09 5:51 ` Johannes Thumshirn
2024-07-05 15:13 ` [PATCH v4 4/7] btrfs: stripe-tree: add selftests Johannes Thumshirn
2024-07-05 15:13 ` [PATCH v4 5/7] btrfs: don't hold dev_replace rwsem over whole of btrfs_map_block Johannes Thumshirn
2024-07-05 23:28 ` Qu Wenruo
2024-07-05 15:13 ` [PATCH v4 6/7] btrfs: rename brtfs_io_stripe::is_scrub to commit_root Johannes Thumshirn
2024-07-05 23:32 ` Qu Wenruo
2024-07-05 15:13 ` [PATCH v4 7/7] btrfs: stripe-tree: also look at commit root on relocation Johannes Thumshirn
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=20240705-b4-rst-updates-v4-0-f3eed3f2cfad@kernel.org \
--to=jth@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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