From: Larry McVoy <lm@bitmover.com>
To: "Henning P. Schmiedehausen" <hps@intermeta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bkbits.net down
Date: Fri, 29 Mar 2002 11:18:33 -0800 [thread overview]
Message-ID: <20020329111833.B6490@work.bitmover.com> (raw)
In-Reply-To: <200203271853.g2RIrRv11812@work.bitmover.com> <20020327222738.B16149@work.bitmover.com> <20020328112252.F22352@work.bitmover.com> <a81gte$hrj$1@forge.intermeta.de>
On Fri, Mar 29, 2002 at 10:50:22AM +0000, Henning P. Schmiedehausen wrote:
> Larry McVoy <lm@bitmover.com> writes:
>
> >The drive has bad blocks and when it hits them it goes into retry la la land,
> >so I won't know which data is bad until I hit the bad blocks.
>
> You've learned now the hard way why integrity checks in an application
> will never be able to replace things like backups or RAID systems.
> Maybe you want to reread the flamewar^Wthread from some time ago with
> your new knowledge.
You obviously didn't read that thread. Both in the context of
BitKeeper and in the context of normal data, you would have seen that
we have backups, we just have backups that we can verify are correct.
The repositories on bkbits.net are automirrored after each incoming event.
There were a few ppc ones which were not and we're still trying to figure
out why, and things like the .ssh keys were not completely backed up;
we're fixing that by putting that information into a BK repository so
it will just automirror like everything else.
I'm not sure why you yanking my chain, it's counter productive and
flat out rude after I just spent two days doing nothing but putting
things back together for kernel developers. What, exactly, did you
hope to accomplish?
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-03-29 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 18:53 bkbits.net down root
2002-03-28 1:54 ` Mike Fedyk
2002-03-28 6:27 ` Larry McVoy
2002-03-28 6:54 ` Petko Manolov
2002-03-28 19:22 ` Larry McVoy
2002-03-29 10:50 ` Henning P. Schmiedehausen
2002-03-29 19:18 ` Larry McVoy [this message]
2002-03-29 22:44 ` Henning P. Schmiedehausen
2002-03-29 22:49 ` Larry McVoy
2002-03-29 1:29 ` Larry McVoy
2002-03-29 13:38 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-03-29 14:35 hatefullinuxuser
2002-10-07 3:06 Larry McVoy
2002-10-07 15:15 ` Aaron Lehmann
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=20020329111833.B6490@work.bitmover.com \
--to=lm@bitmover.com \
--cc=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.org \
/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