From: Jeff Garzik <jeff@garzik.org>
To: David Lang <dlang@digitalinsight.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Compression and dictionaries
Date: Mon, 14 Aug 2006 13:50:31 -0400 [thread overview]
Message-ID: <44E0B7E7.6020207@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0608141033080.14796@qynat.qvtvafvgr.pbz>
David Lang wrote:
> that would only tell you that what you have is garbage (and you need to
> restore from backup(, useing a ECC costs some space, but lets you
> recover from some errors without having to resort to backups.
ECC permits you to recover from very specific, very-limited-damage
scenarios like bit errors.
On modern hard drives, single-bit data corruption is very very very rare
(particularly since ECC is already employed on the platter).
Jeff
next prev parent reply other threads:[~2006-08-14 17:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 3:37 Compression and dictionaries Jon Smirl
2006-08-14 3:56 ` Shawn Pearce
2006-08-14 4:07 ` Jon Smirl
2006-08-14 4:17 ` Shawn Pearce
2006-08-14 7:48 ` Alex Riesen
2006-08-14 10:06 ` Erik Mouw
2006-08-14 12:33 ` Johannes Schindelin
2006-08-14 14:08 ` Jon Smirl
2006-08-14 14:45 ` Johannes Schindelin
2006-08-14 16:15 ` Jon Smirl
2006-08-14 16:32 ` David Lang
2006-08-14 16:55 ` Jakub Narebski
2006-08-14 17:15 ` Jeff Garzik
2006-08-14 17:34 ` David Lang
2006-08-14 17:50 ` Jeff Garzik [this message]
2006-08-14 18:48 ` Jon Smirl
2006-08-14 19:08 ` David Lang
2006-08-14 19:38 ` Johannes Schindelin
2006-08-14 15:14 ` Alex Riesen
2006-08-14 15:26 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2006-08-15 8:33 linux
2006-08-15 13:29 ` Jon Smirl
2006-08-15 14:55 ` Jon Smirl
2006-08-16 0:37 ` linux
[not found] ` <4b73d43f0608152243i15b37036x7aa50aa3afc2b02f@mail.gmail.com>
2006-08-16 5:50 ` Jon Smirl
2006-08-16 6:33 ` Johannes Schindelin
2006-08-16 6:55 ` Shawn Pearce
2006-08-16 7:09 ` Johannes Schindelin
2006-08-16 14:43 ` Jon Smirl
2006-08-17 22:33 ` linux
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=44E0B7E7.6020207@garzik.org \
--to=jeff@garzik.org \
--cc=dlang@digitalinsight.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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 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.