linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: chainofflowers <chainofflowers@neuromante.net>,
	Forza <forza@tnonline.net>,
	linux-btrfs@vger.kernel.org, Justin.Brown@fandingo.org,
	Qu Wenruo <wqu@suse.com>
Subject: Re: Access Beyond End of Device & Input/Output Errors
Date: Sun, 25 Apr 2021 06:56:17 +0800	[thread overview]
Message-ID: <a954b5b7-1df8-0592-7116-1818b17f03cd@gmx.com> (raw)
In-Reply-To: <1706720.PQSuIbNzif@luna>



On 2021/4/24 下午10:13, chainofflowers wrote:
> On Samstag, 24. April 2021 02:25 Qu Wenruo wrote:
>> But if that's the case, btrfs-check should be able to report such
>> problem from the very beginning.
>
> btrfs check was only reporting that "the cache would have been invalidated", I
> don't know if that was enough to suggest that a cache clear was needed.

That means the cache generation is not matching super block generation.
Kernel is good enough to detect such case and ignore the cache.

  I
> assumed it would have done it automatically the next time the volume was
> mounted, that's why I didn't clean it... "pro-actively".
>
> Could "clear-ino-cache" have helped, or not at all?

ino-cache is a feature that is mostly deprecated, and no known
real-world usage.

Thanks,
Qu

>
>
> (c)
>

  reply	other threads:[~2021-04-24 22:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 23:38 Access Beyond End of Device & Input/Output Errors chainofflowers
2021-01-18  0:11 ` Qu Wenruo
2021-01-18 21:07   ` chainofflowers
2021-01-21 23:55     ` chainofflowers
2021-01-22  0:49       ` Qu Wenruo
2021-02-08 21:05         ` chainofflowers
2021-02-20 11:26           ` chainofflowers
2021-02-20 11:42             ` Qu Wenruo
2021-02-20 11:46           ` Forza
2021-02-20 12:07             ` chainofflowers
2021-02-20 12:13               ` Qu Wenruo
2021-04-23 23:36                 ` chainofflowers
2021-04-24  0:25                   ` Qu Wenruo
2021-04-24 14:13                     ` chainofflowers
2021-04-24 22:56                       ` Qu Wenruo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-01  6:51 Justin Brown
2020-08-01  6:58 ` Qu Wenruo
2020-08-01  7:02   ` Qu Wenruo
     [not found]     ` <CAKZK7uzmg19NDjGPPAxXKu7LJ-7ZdHu2cad22csj_chr2qxMJg@mail.gmail.com>
2020-08-01  9:31       ` Qu Wenruo
2020-08-01 11:56         ` Justin Brown
2020-08-01 23:30           ` Qu Wenruo
2020-09-06  1:42             ` Justin Brown

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=a954b5b7-1df8-0592-7116-1818b17f03cd@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=Justin.Brown@fandingo.org \
    --cc=chainofflowers@neuromante.net \
    --cc=forza@tnonline.net \
    --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;
as well as URLs for NNTP newsgroup(s).