From: Chris Mason <chris.mason@oracle.com>
To: Martin Schitter <ms@mur.at>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs csum failed
Date: Wed, 04 May 2011 08:39:10 -0400 [thread overview]
Message-ID: <1304512672-sup-1948@think> (raw)
In-Reply-To: <4DC07A10.7070200@mur.at>
Excerpts from Martin Schitter's message of 2011-05-03 17:56:32 -0400:
> since my last debian kernel-update to 2.6.38-2-amd64 i got troubles with
> csum failures. it's a volume full of huge kvm-images on md-RAID1 and
> LVM, so i used the mount options: 'noatime,nodatasum' to maximize the
> performance.
>
> it happened two weeks ago for the fist time. and now again a kvm-image
> isn't readable again. i have to use an older snapshot to substitute the
> virtual machine.
>
> this are the entries in dmesg/kernel-log on any access:
> ...
> [2412668.409442] btrfs csum failed ino 258 off 2331529216 csum
> 3632892464 private 2115348581
> ...
>
> it's a production machine, so i can not make to much experiments on it.
> do you see an obvious way to solve this problem?
What OS is inside these virtual machines? The btrfs unstable tree has
some fixes for windows based OSes.
Is your kvm config using 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.
-chris
next prev parent reply other threads:[~2011-05-04 12:39 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 [this message]
2011-05-04 14:06 ` Martin Schitter
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=1304512672-sup-1948@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ms@mur.at \
/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).