public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Torcz <tomek@pipebreaker.pl>
To: Jens Axboe <jens.axboe@oracle.com>
Subject: Re: btrfs csum failed on git .pack file
Date: Tue, 8 Sep 2009 22:55:41 +0200	[thread overview]
Message-ID: <20090908205541.GC4247@mother.pipebreaker.pl> (raw)
In-Reply-To: <20090908203214.GH18599@kernel.dk>

On Tue, Sep 08, 2009 at 10:32:14PM +0200, Jens Axboe wrote:
> On Tue, Sep 08 2009, Markus Trippelsdorf wrote:
> > On Tue, Sep 08, 2009 at 10:00:42PM +0200, Jens Axboe wrote:
> > > On Mon, Sep 07 2009, Markus Trippelsdorf wrote:
> > > > Just got this error today in my dmesg:
> > > > btrfs csum failed ino 1483065 off 158482432 csum 4283543305 private 43905798
> > 
> > I've already deleted the file in question unfortunately.
> > On IRC Chris decided that either bad RAM or a harddrive error was the
> > most likely reason for this chechsum mismatch.
> 
> Darn, that's too bad. The corruption issue I had was also in a git pack
> file. It was fine one day, bad the next. Turned out to be 16kb of 0xff
> in the file, and I blamed it on the (cheap) SSD drive that hosted the
> local git repo. It's still the most likely explanation given the nature
> of the problem, however it would have been really interesting to see
> what corruption you had.

  BTW, I had some similar issue. One file on btrfs had csum failed.
I've copied it using dd_rescue and, suprise, reading new file yields
this error also. How to retrieve block failing csum check from btrfs volume?

-- 
Tomasz Torcz                                                       72->|   80->|
xmpp: zdzichubg@chrome.pl                                          72->|   80->|


  reply	other threads:[~2009-09-08 20:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 20:35 btrfs csum failed on git .pack file Markus Trippelsdorf
2009-09-08 20:00 ` Jens Axboe
2009-09-08 20:22   ` Markus Trippelsdorf
2009-09-08 20:32     ` Jens Axboe
2009-09-08 20:55       ` Tomasz Torcz [this message]
2009-09-09  6:55       ` Markus Trippelsdorf
2009-09-09  7:01         ` Jens Axboe
2009-09-09  7:23           ` Markus Trippelsdorf
2009-09-09  7:29             ` Jens Axboe
2009-09-09  8:18           ` Daniel J Blueman
2009-09-09  8:26             ` Jens Axboe
2009-09-09  8:37               ` Daniel J Blueman
2009-09-09 11:19                 ` Chris Mason
2009-09-09 21:01           ` Oliver Mattos
2009-09-10 10:49             ` Bryan Østergaard
2009-09-08 21:53     ` Tracy Reed
2009-09-09  7:28       ` Gregory Maxwell
2009-09-17  5:05   ` Markus Trippelsdorf
2009-09-17  6:44     ` Jens Axboe
2009-09-17  9:04       ` Markus Trippelsdorf
2009-09-17  9:05         ` Jens Axboe
2009-09-17 12:15           ` Markus Trippelsdorf
2009-09-17 13:58             ` Markus Trippelsdorf
2009-09-17 17:00             ` Zach Brown
2009-09-17 17:10               ` Markus Trippelsdorf
2009-09-17 17:50                 ` Tomasz Torcz

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=20090908205541.GC4247@mother.pipebreaker.pl \
    --to=tomek@pipebreaker.pl \
    --cc=jens.axboe@oracle.com \
    /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