public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bryan Østergaard" <bryan.ostergaard@gmail.com>
To: Oliver Mattos <oliver.mattos08@imperial.ac.uk>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	Markus Trippelsdorf <markus@trippelsdorf.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs csum failed on git .pack file
Date: Thu, 10 Sep 2009 12:49:58 +0200	[thread overview]
Message-ID: <73967b650909100349o377174c0kc84a8d3ea2cc3001@mail.gmail.com> (raw)
In-Reply-To: <21A769F737B64494B43804084FB1EF88@home.omattos.com>

On Wed, Sep 9, 2009 at 11:01 PM, Oliver Mattos
<oliver.mattos08@imperial.ac.uk> wrote:
>
>>> What a strange coincidence that it affected git pack files in both =
cases.
>>> It's almost too improbable...
>
I had similar problems with a broken git repository about two weeks
ago. This was on a regular laptop harddrive that's never reported any
errors.

Unfortunately I rm'ed the repository and cloned it again so I can't
check exactly what caused the corruption. Interestingly I've just
discovered a broken tar.bz2 file that shows similar symptoms as what's
been described here earlier.

The first (and by far largest) chunk of the file consists entirely of
0x01 bytes followed by a smaller chunk that appears to be a PNG file
and then arch/sparc/include/asm/fhc.h from the linux kernel. After
this I have a small chunk of 0x00 bytes followed by
arch/sparc/include/asm/floppy.h.

This pattern is repeated several times with different include files
from the kernel sources and the file ends with a small chunk of 0x01
bytes again.

The harddisk in question is:
=3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D
Model Family:     Fujitsu MHV series
Device Model:     FUJITSU MHV2080BH
Serial Number:    NW05T6425FRY
=46irmware Version: 00840028
User Capacity:    80,025,280,000 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 4a
Local Time is:    Thu Sep 10 12:40:10 2009 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

As already mentioned it's never reported any errors and I also haven't
seen any problems like this before when using ext3 or ext4. The broken
file is available at http://omploader.org/vMmJtbg if that's any help.

Regards,
Bryan =D8stergaard
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-09-10 10:49 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 [this message]
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=73967b650909100349o377174c0kc84a8d3ea2cc3001@mail.gmail.com \
    --to=bryan.ostergaard@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=oliver.mattos08@imperial.ac.uk \
    /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