linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Arnaldo Montagner <armont@google.com>
Cc: Bcache Linux <linux-bcache@vger.kernel.org>
Subject: Re: I/O error on cache device can cause user observable errors
Date: Sat, 3 Feb 2024 11:43:24 +0800	[thread overview]
Message-ID: <E73B372A-F347-42A3-955E-A0DEA5B08C3E@suse.de> (raw)
In-Reply-To: <CANF=pgrictityuTm4Uv_KqUn=LnbSf9VW7-EMYUS+MvCSdMqvQ@mail.gmail.com>



> 2024年2月3日 01:48,Arnaldo Montagner <armont@google.com> 写道:
> 
> Thanks for clarifying.
> 
> Regarding the documentation, the first sentence in
> https://docs.kernel.org/admin-guide/bcache.html#error-handling says:
> "Bcache tries to transparently handle IO errors to/from the cache
> device without affecting normal operation"
> 

Oh I see. This is for temporary I/O failure or error. If cache is clear and an I/O error encountered, bcache may fetch data from backing device.
Such operations are transparent to upper layer code.

> I guess I interpreted it in absolute terms, as some kind of guarantee
> that normal operation would not be affected.
> 

For devices failure or absence, bcache need to make upper layer code to be aware and hand the aftermath when necessary. Your situation is in this category.

Thanks.

Coly Li

      reply	other threads:[~2024-02-03  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 22:25 I/O error on cache device can cause user observable errors Arnaldo Montagner
2024-02-02  7:00 ` Coly Li
2024-02-02 17:48   ` Arnaldo Montagner
2024-02-03  3:43     ` Coly Li [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=E73B372A-F347-42A3-955E-A0DEA5B08C3E@suse.de \
    --to=colyli@suse.de \
    --cc=armont@google.com \
    --cc=linux-bcache@vger.kernel.org \
    /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).