From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add intrudoction to dev-replace.
Date: Thu, 30 Jan 2020 13:46:34 +0100 [thread overview]
Message-ID: <20200130124634.GP3929@twin.jikos.cz> (raw)
In-Reply-To: <20200123074450.24328-1-wqu@suse.com>
On Thu, Jan 23, 2020 at 03:44:50PM +0800, Qu Wenruo wrote:
> The overview of btrfs dev-replace is not that complex.
> But digging into the code directly can waste some extra time, so add
> such introduction to help later guys.
>
> Also, it mentions some corner cases caused by the write duplication and
> scrub based data copy, to inform new comers not to get trapped by that
> pitfall.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Thanks for the docs, I've adjusted some wording and fixed a few typos.
Please try to proofread it before sending, also reviews should catch
and point that out.
next prev parent reply other threads:[~2020-01-30 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 7:44 [PATCH] btrfs: Add intrudoction to dev-replace Qu Wenruo
2020-01-23 8:00 ` Anand Jain
2020-01-30 12:46 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-22 7:20 Qu Wenruo
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=20200130124634.GP3929@twin.jikos.cz \
--to=dsterba@suse.cz \
--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