linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Smutny <philipp.smutny@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Weird checksum error with VM images
Date: Mon, 10 Dec 2012 09:57:42 +0000 (UTC)	[thread overview]
Message-ID: <loom.20121210T102718-486@post.gmane.org> (raw)
In-Reply-To: 1350475643.26001.18.camel@fatty

Hi,

I think I experienced exactly the same issue, with Debian Wheezy, running
kernel 3.6 on an old fashioned spinning hd. I was using a 1GB raw image with
a plain ext2 filesystem running qemu-kvm with the cache=none option and I
got a lot of:

Dec  6 21:19:59 hephaistos kernel: [  664.769629] btrfs csum failed ino
693974 off 470827008 csum 3711077113 private 141102393

I could still copy the first ~470MB of the raw image and save the only file,
that was important to me. Scrub was unable to fix it, but showed no further
errors.

Philipp


      reply	other threads:[~2012-12-10  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 12:07 Weird checksum error with VM images Alexander Larsson
2012-12-10  9:57 ` Philipp Smutny [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=loom.20121210T102718-486@post.gmane.org \
    --to=philipp.smutny@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).