From: Anton Shepelev <anton.txt@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: CRC mismatch
Date: Thu, 18 Oct 2018 15:02:28 +0300 [thread overview]
Message-ID: <20181018150228.16680172c2551c06038d5344@gmail.com> (raw)
In-Reply-To: <20181016183051.788a79297af47a9798a0c0e3@gmail.com>
I wrote:
>What may be the reason of a CRC mismatch on a BTRFS file in
>a virutal machine:
>
>csum failed ino 175524 off 1876295680 csum 451760558
>expected csum 1446289185
>
>Shall I seek the culprit in the host machine on in the
>guest one? Supposing the host machine healty, what
>operations on the gueest might have caused a CRC mismatch?
Thank you, Austin and Chris, for your replies. While
describing the problem for the client, I tried again to copy
the corrupt file and this time it was copied without error,
which is of course scary because errors that miraculously
disappear may suddenly reappear in the same manner.
--
() ascii ribbon campaign - against html e-mail
/\ http://preview.tinyurl.com/qcy6mjc [archived]
next prev parent reply other threads:[~2018-10-18 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 15:30 CRC mismatch Anton Shepelev
2018-10-16 15:42 ` Austin S. Hemmelgarn
2018-10-16 20:27 ` Chris Murphy
2018-10-17 9:15 ` Anton Shepelev
2018-10-17 11:59 ` Austin S. Hemmelgarn
2018-10-18 12:02 ` Anton Shepelev [this message]
2018-10-18 12:34 ` Austin S. Hemmelgarn
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=20181018150228.16680172c2551c06038d5344@gmail.com \
--to=anton.txt@gmail.com \
--cc=linux-btrfs@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).