All of lore.kernel.org
 help / color / mirror / Atom feed
From: chainofflowers <chainofflowers@neuromante.net>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, 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: Sat, 24 Apr 2021 16:13:32 +0200	[thread overview]
Message-ID: <1706720.PQSuIbNzif@luna> (raw)
In-Reply-To: <e229a858-79c2-0416-6ab8-14b56177b21d@suse.com>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

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. 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?


(c)


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-24 14:14 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 [this message]
2021-04-24 22:56                       ` Qu Wenruo
  -- 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=1706720.PQSuIbNzif@luna \
    --to=chainofflowers@neuromante.net \
    --cc=Justin.Brown@fandingo.org \
    --cc=forza@tnonline.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.