public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs csum failed on git .pack file
Date: Thu, 17 Sep 2009 11:05:49 +0200	[thread overview]
Message-ID: <20090917090549.GE23126@kernel.dk> (raw)
In-Reply-To: <20090917090428.GA1877@phenom2.trippelsdorf.de>

On Thu, Sep 17 2009, Markus Trippelsdorf wrote:
> On Thu, Sep 17, 2009 at 08:44:56AM +0200, Jens Axboe wrote:
> > On Thu, Sep 17 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
> > > > > 
> > > > > linux % find . -inum 1483065
> > > > > ./.git/objects/pack/pack-f9251bcc6a8afe3c92193e14d1d742f2f0182ce5.pack
> > > > > 
> > > > > It's the main pack file from my git linux kernel tree:
> > > > > 
> > > > 
> > > > Hmm, I ran into something very similar. Care to check what the corrupted
> > > > block of data looks like (and how big it is)?
> > > 
> > > I've hit the same problem again today:
> > > 
> > > btrfs csum failed ino 1826333 off 150208512 csum 4148434891 private 1660028275
> > > 
> > > The file in question is:
> > > ./.git/objects/pack/pack-a2330b703d5a7fd62626b39a5fdfb6eecf739d0d.pack
> > > 
> > > I can't read the file directly, because of the csum mismatch:
> > 
> > Chris, is there a way to force reading the file? Seems like that would
> > be a very handy feature.
> > 
> > Markus, not sure if that works, but you could always try and remount
> > with data checksumming disabled.
> > 
> > mount /dev/fooX -o remount,rw,nodatasum
> > 
> > should do the trick.
> 
> That doesn't work unfortunately, btrfs still calculates and compares the
> checksums (it won't write new ones I guess).

Ah ok, as mentioned I wasn't sure whether that would work or not. I'll
defer to Chris :-)

-- 
Jens Axboe


  reply	other threads:[~2009-09-17  9:05 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
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 [this message]
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=20090917090549.GE23126@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    /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