public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: bkbits.net down
Date: Fri, 29 Mar 2002 10:50:22 +0000 (UTC)	[thread overview]
Message-ID: <a81gte$hrj$1@forge.intermeta.de> (raw)
In-Reply-To: <200203271853.g2RIrRv11812@work.bitmover.com> <20020327222738.B16149@work.bitmover.com> <20020328112252.F22352@work.bitmover.com>

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.

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  reply	other threads:[~2002-03-29 10:50 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 [this message]
2002-03-29 19:18       ` Larry McVoy
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='a81gte$hrj$1@forge.intermeta.de' \
    --to=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