From: Tracy Reed <treed@ultraviolet.org>
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: Tue, 8 Sep 2009 14:53:57 -0700 [thread overview]
Message-ID: <20090908215357.GK6779@tracyreed.org> (raw)
In-Reply-To: <20090908202211.GA1901@phenom2.trippelsdorf.de>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Tue, Sep 08, 2009 at 10:22:11PM +0200, Markus Trippelsdorf spake thusly:
> 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.
Which raises an interesting point: I know reiserfs had its problems
but it also turned up a lot of machines with bad RAM which contributed
to giving the fs a bad name. With more and more complicated and memory
consuming filesystem datastructures being stored in RAM, larger volumes
of RAM in systems, and RAM not really getting any more reliable will
we ever see a day where something like btrfs is not recommended for
use in any machine that doesn't have ECC? Does the filesystem do
anything to protect itself from bad hardware?
--
Tracy Reed
http://tracyreed.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-09-08 21:53 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 [this message]
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=20090908215357.GK6779@tracyreed.org \
--to=treed@ultraviolet.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox