From: Martin Schitter <ms@mur.at>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs csum failed
Date: Wed, 04 May 2011 16:06:58 +0200 [thread overview]
Message-ID: <4DC15D82.40802@mur.at> (raw)
In-Reply-To: <1304512672-sup-1948@think>
Am 2011-05-04 14:39, schrieb Chris Mason:
> What OS is inside these virtual machines? The btrfs unstable tree has
> some fixes for windows based OSes.
we have only linux guests of different flavor, no windows guests.
both corruptions during this last weeks belong to different virtual
block device images of the same guest instance.
> Is your kvm config using O_DIRECT?
yes -- the kvm/qemu option cache="none" implies O_DIRECT.
> I've also got patches here that force us to honor nodatasum even when
> the file has csums, that can help if the contents of the file are
> actually good.
that sounds interessting! in our case it may be easier do use same
recent backup data, but it could be very helpful in similar situations.
i would really like to help isolating the reasons of this failure and a
find a practical strategy to prevent additional breakdowns.
thanks
martin
prev parent reply other threads:[~2011-05-04 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 21:56 btrfs csum failed Martin Schitter
2011-05-04 0:28 ` Josef Bacik
2011-05-04 0:44 ` Martin Schitter
2011-05-04 2:18 ` Fajar A. Nugraha
2011-05-04 11:39 ` Martin Schitter
2011-05-04 11:47 ` Hugo Mills
2011-05-04 11:51 ` cwillu
2011-05-04 12:27 ` Martin Schitter
2011-05-04 13:23 ` Edward Ned Harvey
2011-05-04 14:42 ` Martin Schitter
2011-05-04 18:10 ` Chris Mason
2011-05-04 14:09 ` Jan Schmidt
2011-05-04 12:31 ` Kaspar Schleiser
2011-05-04 13:25 ` Martin Schitter
2011-05-04 14:39 ` Josef Bacik
2011-05-04 12:39 ` Chris Mason
2011-05-04 14:06 ` Martin Schitter [this message]
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=4DC15D82.40802@mur.at \
--to=ms@mur.at \
--cc=chris.mason@oracle.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).