From: Anton Shepelev <anton.txt@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: CRC mismatch
Date: Wed, 17 Oct 2018 12:15:44 +0300 [thread overview]
Message-ID: <20181017121544.3d5e310a9266747d2367c871@gmail.com> (raw)
In-Reply-To: <CAJCQCtRrqOf+AzkH+-z++GTx9+Mh0-wA5PqQB9g0kDhBBCJ2qQ@mail.gmail.com>
[I accdientally replied to Chris instead of the mailing list]
Chris Murphy:
>Is there still that O_DIRECT related "bug" (or more of a
>limitation) if the guest is using cache=none on the block
>device?
I know nothing about it.
>Anton what virtual machine tech are you using? qemu/kvm
>managed with virt-manager? The configuration affects host
>behavior; but the negative effect manifests inside the
>guest as corruption. If I remember correctly.
This is a commericial system run inside VMWare.
--
() ascii ribbon campaign - against html e-mail
/\ http://preview.tinyurl.com/qcy6mjc [archived]
next prev parent reply other threads:[~2018-10-17 9:15 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 [this message]
2018-10-17 11:59 ` Austin S. Hemmelgarn
2018-10-18 12:02 ` Anton Shepelev
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=20181017121544.3d5e310a9266747d2367c871@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).