From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
dsterba@suse.cz, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: scrub: Require mandatory block group RO for dev-replace
Date: Fri, 24 Jan 2020 14:40:55 +0100 [thread overview]
Message-ID: <20200124134055.GH3929@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H5FRdvnxG4KQhLTaaHFcP_bMUQsOxoJxfQwi8L8npGxDA@mail.gmail.com>
On Fri, Jan 24, 2020 at 09:24:50AM +0000, Filipe Manana wrote:
> On Fri, Jan 24, 2020 at 12:07 AM Qu Wenruo <wqu@suse.com> wrote:
> > Reported-by: Filipe Manana <fdmanana@suse.com>
> > Fixes: 76a8efa171bf ("btrfs: Continue replace when set_block_ro failed")
> > Fixes: b12de52896c0 ("btrfs: scrub: Don't check free space before marking a block group RO")
> > Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> Reviewed-by: Filipe Manana <fdmanana@suse.com>
>
> Now it looks good, thanks!
Thank you both, patch on the way to 5.5-rc8 or 5.6 final.
next prev parent reply other threads:[~2020-01-24 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 23:58 [PATCH] btrfs: scrub: Require mandatory block group RO for dev-replace Qu Wenruo
2020-01-24 9:24 ` Filipe Manana
2020-01-24 13:40 ` David Sterba [this message]
2020-01-24 14:44 ` David Sterba
2020-01-24 16:28 ` Filipe Manana
2020-01-25 0:36 ` Qu Wenruo
2020-01-25 0:48 ` Qu Wenruo
2020-01-25 11:35 ` David Sterba
2020-01-25 12:09 ` Qu WenRuo
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 7:37 Qu Wenruo
2020-01-23 12:06 ` Filipe Manana
2020-01-23 12:28 ` Qu WenRuo
2020-01-23 13:39 ` Qu Wenruo
2020-01-23 13:49 ` Filipe Manana
2020-01-23 13:57 ` Qu Wenruo
2020-01-23 16:40 ` David Sterba
2020-01-23 23:58 ` 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=20200124134055.GH3929@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@gmail.com \
--cc=fdmanana@suse.com \
--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