From: zhangzhen.email@gmail.com
To: Coly Li <colyli@suse.de>, Nix <nix@esperi.org.uk>,
linux-bcache@vger.kernel.org, jianchao.wan9@gmail.com
Subject: Re: bcache detach lead to xfs force shutdown
Date: Mon, 7 Mar 2022 17:06:41 +0800 [thread overview]
Message-ID: <96ae0c81-c4a4-240c-9d5a-965c4474db2b@gmail.com> (raw)
In-Reply-To: <2c6244b9-249a-3379-31b5-f16b3d0cb162@suse.de>
On 3/7/22 4:21 PM, Coly Li <colyli@suse.de> wrote:
> On 3/7/22 3:56 PM, zhangzhen.email@gmail.com wrote:
>
> >> >>
> >> >> Hold on. Why do you think it should be fixed? As I said, it is >>
> >> as-designed behavior.
> >> >>
> >> > We use bcache in writearound mode, just cache read io.
> >> > Currently, bcache return io error during detach, randomly lead to
> >> > xfs force shutdown.
> >> >
> >> > After bcache auto detach finished, some dir read write normaly, but
> >> > the others can't read write because of xfs force shutdown.
> >> > This inconsistency confuses filesystem users.
> >>
> >>
> >> Hi Zhen and Nix,
> >>
> >> OK, I come to realize the motivation. Yes you are right, this is an
> >> awkward issue and good to be fixed.
> >>
> > Hi Coly,
> >
> > So you will pick this patch into your tree ？
>
>
> I need to look the patch firstly, could you please post a proposal patch
> for review ?
Ok.
>
>
> Coly Li
>
>
next prev parent reply other threads:[~2022-03-07 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 9:33 bcache detach lead to xfs force shutdown Zhang Zhen
2022-02-23 9:03 ` Coly Li
2022-02-23 12:26 ` Zhang Zhen
2022-03-02 9:19 ` Coly Li
2022-03-03 17:42 ` Nix
2022-03-04 8:22 ` Zhang Zhen
2022-03-04 8:42 ` Coly Li
2022-03-07 7:56 ` zhangzhen.email
2022-03-07 8:21 ` Coly Li
2022-03-07 9:06 ` zhangzhen.email [this message]
2022-03-07 9:16 ` [PATCH] Bcache: don't return BLK_STS_IOERR during cache detach Zhen Zhang
2022-03-09 13:14 ` bcache detach lead to xfs force shutdown Coly Li
2022-03-10 2:01 ` Zhang Zhen
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=96ae0c81-c4a4-240c-9d5a-965c4474db2b@gmail.com \
--to=zhangzhen.email@gmail.com \
--cc=colyli@suse.de \
--cc=jianchao.wan9@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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