From: Johannes Thumshirn <jth@kernel.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, Johannes Thumshirn <jth@kernel.org>
Subject: [RFC 0/2] Add dummy RAID stripe tree entries for PREALLOC data
Date: Wed, 18 Sep 2024 16:08:48 +0200 [thread overview]
Message-ID: <20240918140850.27261-1-jth@kernel.org> (raw)
In-Reply-To: <85888aaa-c8f5-453b-8344-6cabc82f537e@gmx.com>
This is an RFC implementation of Qu's request to be able to
distinguish preallocated extents in the stripe tree for scrub.
It's not 100% working yet but only showing the basic "how it's going to
look like".
I'm not really sure this is a better solution than returning ENOENT
and ignoring it in scrub.
A third possibility would be to do a full backref walk on
btrfs_map_block() error and then check if it's a preallocated extent.
Johannes Thumshirn (2):
btrfs: introduce dummy RAID stripes for preallocated data
btrfs: insert dummy RAID stripe extents for preallocated data
fs/btrfs/inode.c | 47 +++++++++++++++++++++++++++++++++
fs/btrfs/raid-stripe-tree.c | 47 +++++++++++++++++++++++++++++++++
fs/btrfs/raid-stripe-tree.h | 2 ++
include/uapi/linux/btrfs_tree.h | 1 +
4 files changed, 97 insertions(+)
--
2.43.0
next prev parent reply other threads:[~2024-09-18 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 14:33 [PATCH] btrfs: scrub: skip PREALLOC extents on RAID stripe-tree Johannes Thumshirn
2024-09-12 21:32 ` Qu Wenruo
2024-09-13 5:42 ` Johannes Thumshirn
2024-09-13 5:47 ` Qu Wenruo
2024-09-18 14:08 ` Johannes Thumshirn [this message]
2024-09-18 14:08 ` [RFC 1/2] btrfs: introduce dummy RAID stripes for preallocated data Johannes Thumshirn
2024-09-18 14:08 ` [RFC 2/2] btrfs: insert dummy RAID stripe extents " Johannes Thumshirn
2024-09-18 23:45 ` [RFC 0/2] Add dummy RAID stripe tree entries for PREALLOC data Qu Wenruo
2024-09-19 15:42 ` Johannes Thumshirn
2024-09-19 16:57 ` Gerhard Wiesinger
2024-09-20 9:50 ` Johannes Thumshirn
2024-09-23 15:27 ` Josef Bacik
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=20240918140850.27261-1-jth@kernel.org \
--to=jth@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).