From: Zach Brown <zach.brown@oracle.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Jens Axboe <jens.axboe@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs csum failed on git .pack file
Date: Thu, 17 Sep 2009 10:00:28 -0700 [thread overview]
Message-ID: <4AB26B2C.9030703@oracle.com> (raw)
In-Reply-To: <20090917121501.GB1877@phenom2.trippelsdorf.de>
> 0130 9FA0: E2 3B 43 AA 63 BF 28 B3 87 B7 FD AB DA 74 2D 1C
> 0130 9FA0: E2 3B 43 AA 63 BF 28 B3 87 33 FD AB DA 74 2D 1C
B7 = 10110111
33 = 00110011
> 06CD DF90: B0 22 6B 46 9F ED 6E 47 73 5E 7E EB DA 5F D6 11
> 06CD DF90: B0 22 6B 46 9F ED 6E 47 73 1E 7E EB DA 5F D6 11
5E = 01011110
1E = 00011110
> 06CD DFC0: 0D 86 2B B2 57 A4 5A CD 78 4B 08 94 C0 65 17 3A
> 06CD DFC0: 0D 86 2B B2 57 A4 5A CD 78 0B 08 94 C0 65 17 3A
4B = 01001011
0B = 00001011
And so on.
It looks like a few bits are getting flipped at the same byte offset.
One can imagine software bugs that would do this, certainly, but upset
hardware seems awfully likely too.
- z
next prev parent reply other threads:[~2009-09-17 17:00 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
2009-09-17 12:15 ` Markus Trippelsdorf
2009-09-17 13:58 ` Markus Trippelsdorf
2009-09-17 17:00 ` Zach Brown [this message]
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=4AB26B2C.9030703@oracle.com \
--to=zach.brown@oracle.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.