From: chainofflowers <chainofflowers@neuromante.net>
To: Forza <forza@tnonline.net>,
linux-btrfs@vger.kernel.org, quwenruo.btrfs@gmx.com
Subject: Re: Access Beyond End of Device & Input/Output Errors
Date: Sat, 20 Feb 2021 13:07:52 +0100 [thread overview]
Message-ID: <76971f62-d050-fac2-1694-71d3115e1bf7@neuromante.net> (raw)
In-Reply-To: <e179094e-8926-beee-92b7-0885f1665f89@tnonline.net>
On 20.02.21 12:46, Forza wrote:
> Are you using fstrim by any chance? Could the problem be related to
> https://patchwork.kernel.org/project/fstests/patch/20200730121735.55389-1-wqu@suse.com/
Yes, that's what I mentioned in my first post.
Actually, it all started with the bug with dm, but some similar
behaviour persists even after that bug was fixed:
https://lore.kernel.org/linux-btrfs/20190521190023.GA68070@glet/T/
The only "maybe unusual" thing in my setup is that I use btrfs on the
top of dmcrypt directly, without lvm in-between, but I am not the only
one...
@Qu:
My RAM looks OK so far, I also thought of that, and I actually ran
memtest for 12+ hours and more than once. I would exclude that case.
I will do a "btrfs check --check-data-csum" and let you know.
In the meantime, I thought of a related question:
-> When a data-csum is corrupted (for whatever reason), is there a
chance that the corruption persists when I copy the whole file system
over to a new one?
As I said previously, I copied the whole fs to new, virgin SSDs more
than once with "rsync -avAHX", and I couldn't spot any issue related to
the copy itself...
(please help! ;-))
(c)
next prev parent reply other threads:[~2021-02-20 12:08 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 [this message]
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
-- 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=76971f62-d050-fac2-1694-71d3115e1bf7@neuromante.net \
--to=chainofflowers@neuromante.net \
--cc=forza@tnonline.net \
--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 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.