From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] Irwin 285
Date: Fri, 22 Jan 2010 07:38:25 -0800 [thread overview]
Message-ID: <20100122153825.GA22757@bitmover.com> (raw)
In-Reply-To: <20100122111557.11f08ebc.jkunz@unixag-kl.fh-kl.de>
On Fri, Jan 22, 2010 at 11:15:57AM +0100, Jochen Kunz wrote:
> On Fri, 22 Jan 2010 10:34:09 +0100
> Wilko Bulte <wb at freebie.xs4all.nl> wrote:
>
> > recoverable read error rate I presume.
> No. NON-recoverable read error rate: 1 per 10^14 bits.
>
> And this is for light desktop use. Heavy IO on the disk may increase
> failure rate. At least this is written in the technical data sheet of
> the drive. WD drives are not that much better: 1 per 10^15 bits.
You guys are funny. I've been doing backups for at least 15 years
and I can tell you story after story about tape failures that
happened to me personally (anyone remember the lovely exabyte 8200,
"fondly" remembered as the write-only device?). On the other hand,
disks work pretty well and when they fail, they fail in little
chunks and you can almost always get the rest of the data.
For the data I really care about, our digital photo collection, it's
all stored in BitKeeper's so-called binary asset management (BAM).
All the data is CRC-ed, it's all replicated, and if anything goes
bad the bad data can easily be replaced from any of the other
(populated) replicas. I periodically run "bk bam check" which
goes through all the data and checks the crc's and have yet to
see an error. Been doing that for years.
Tape. Bah. You can keep it, I'm OK with disk.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2010-01-22 15:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 10:26 Sergey Lapin
2010-01-21 10:51 ` Brantley Coile
2010-01-21 11:19 ` Jochen Kunz
2010-01-21 11:32 ` Wilko Bulte
2010-01-21 12:07 ` Sergey Lapin
2010-01-21 12:37 ` Jason Stevens
2010-01-21 13:02 ` Wilko Bulte
2010-01-21 16:50 ` Jochen Kunz
2010-01-21 17:11 ` Jochen Kunz
2010-01-21 17:37 ` M. Warner Losh
2010-01-21 17:41 ` Sergey Lapin
2010-01-21 19:00 ` Jochen Kunz
2010-01-21 19:10 ` Al Kossow
2010-01-21 19:36 ` Jochen Kunz
2010-01-21 19:41 ` Wilko Bulte
2010-01-21 19:45 ` John Cowan
2010-01-21 18:59 ` Wilko Bulte
2010-01-21 19:48 ` Jochen Kunz
2010-01-21 19:56 ` Wilko Bulte
2010-01-21 19:58 ` Larry McVoy
2010-01-21 20:00 ` Wilko Bulte
2010-01-21 20:11 ` Larry McVoy
2010-01-21 20:26 ` Jason Stevens
2010-01-21 20:41 ` Wilko Bulte
2010-01-21 20:44 ` Larry McVoy
2010-01-21 21:00 ` Wilko Bulte
2010-01-21 21:01 ` Larry McVoy
2010-01-21 21:36 ` lyricalnanoha
2010-01-21 22:15 ` Larry McVoy
2010-01-21 22:22 ` M. Warner Losh
2010-01-22 9:14 ` Jochen Kunz
2010-01-22 9:34 ` Wilko Bulte
2010-01-22 10:15 ` Jochen Kunz
2010-01-22 10:46 ` Wilko Bulte
2010-01-22 11:06 ` Jochen Kunz
2010-01-22 11:12 ` Wilko Bulte
2010-01-22 15:38 ` Larry McVoy [this message]
2010-01-22 16:52 ` Jochen Kunz
2010-01-22 16:55 ` Wilko Bulte
2010-01-21 20:46 ` Jason Stevens
2010-01-21 22:15 ` Aaron J. Grier
2010-01-21 22:57 ` Wilko Bulte
2010-01-21 20:36 ` Wilko Bulte
2010-01-21 20:44 ` Corey Lindsly
2010-01-21 21:45 ` Wilko Bulte
2010-01-22 0:36 ` [TUHS] Backup software (was: Irwin 285) Greg 'groggy' Lehey
2010-01-22 0:48 ` Jason Stevens
2010-01-28 20:27 ` Brad Spencer
2010-02-12 17:03 ` Tim Bradshaw
2010-02-15 1:19 ` [TUHS] dump(8) compatibility (was: Backup software (was: Irwin 285)) Greg 'groggy' Lehey
2010-02-15 1:24 ` Jason Stevens
2010-02-15 1:30 ` [TUHS] dump(8) compatibility M. Warner Losh
2010-02-15 2:27 ` Larry McVoy
2010-02-15 5:05 ` Warner Losh
2010-02-15 5:18 ` Jason Stevens
2010-01-21 20:33 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 20:44 ` Wilko Bulte
2010-01-21 20:47 ` Larry McVoy
2010-01-22 9:23 ` Jochen Kunz
2010-01-22 9:32 ` Wilko Bulte
2010-01-22 0:38 ` [TUHS] Tape backups? (was: Irwin 285) Greg 'groggy' Lehey
2010-01-21 20:18 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 12:05 ` Andrzej Popielewicz
2010-01-21 12:12 ` Sergey Lapin
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=20100122153825.GA22757@bitmover.com \
--to=lm@bitmover.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).