From: Chris Murphy <lists@colorremedies.com>
To: Michal Soltys <msoltyspl@yandex.pl>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: many csum warning/errors on qemu guests using btrfs
Date: Wed, 29 Apr 2020 13:21:33 -0600 [thread overview]
Message-ID: <CAJCQCtTxGRqA4SZFnC+G+=b0bK2ahpym+9eG31pRTv9FH1_-3w@mail.gmail.com> (raw)
In-Reply-To: <76ec883b-3e44-fcda-d981-93a9e120f56d@yandex.pl>
On Wed, Apr 29, 2020 at 9:45 AM Michal Soltys <msoltyspl@yandex.pl> wrote:
>
> Short update:
>
> 1) turned out to not be btrfs fault in any way or form, as we recreated
> the same issue with ext4 while manually checksumming the files; so if
> anything, btrfs told us we have actual issues somewhere =)
>
> 2) qemu/vm scenario is also not to be blamed, as we recreated the issue
> directly on the host as well
>
> So as far as I can see, both of the above narrows the potential culprits
> to either faulty/buggy hardware/firmware somewhere - or - some subtle
> lvm/md/kernel issues. Though so far pinpointing the issue is proving
> rather frustrating.
>
>
> Anyway, sorry for the noise.
It's not noise. I think it's useful to see how Btrfs can help isolate
such cases.
--
Chris Murphy
next prev parent reply other threads:[~2020-04-29 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:23 many csum warning/errors on qemu guests using btrfs Michal Soltys
2020-04-29 15:45 ` Michal Soltys
2020-04-29 19:21 ` Chris Murphy [this message]
2020-04-30 1:46 ` Qu Wenruo
2020-04-30 5:01 ` Chris Murphy
2020-04-30 7:01 ` Qu Wenruo
2020-04-30 13:12 ` Michal Soltys
2020-04-29 19:10 ` Input/output errors (unreadables files) Ferry Toth
2020-04-29 23:45 ` Qu Wenruo
2020-04-30 8:59 ` Ferry Toth
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='CAJCQCtTxGRqA4SZFnC+G+=b0bK2ahpym+9eG31pRTv9FH1_-3w@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=msoltyspl@yandex.pl \
/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).