From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: factor btrfs_check_rw_degradable() to check given device
Date: Tue, 2 Jan 2018 19:01:12 +0100 [thread overview]
Message-ID: <20180102180112.GZ3553@twin.jikos.cz> (raw)
In-Reply-To: <00433e34-a56e-3898-80b9-32a304fe32e2@gmx.com>
On Mon, Dec 18, 2017 at 05:46:59PM +0800, Qu Wenruo wrote:
>
>
> On 2017年12月18日 17:08, Anand Jain wrote:
> > Update btrfs_check_rw_degradable() to check against the given
> > device if its lost.
> >
> > We can use this function to know if the volume is going to be
> > in degraded mode OR failed state, when the given device fails.
> > Which is needed when we are handling the device failed state.
> >
> > A preparatory patch does not affect the flow as such.
> >
> > Signed-off-by: Anand Jain <anand.jain@oracle.com>
>
> Looks good.
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
Added to 4.16 queue, thanks.
prev parent reply other threads:[~2018-01-02 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 9:08 [PATCH] btrfs: factor btrfs_check_rw_degradable() to check given device Anand Jain
2017-12-18 9:46 ` Qu Wenruo
2018-01-02 18:01 ` David Sterba [this message]
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=20180102180112.GZ3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).