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 22:44:54 +0000 (UTC)	[thread overview]
Message-ID: <a82qp6$ps3$1@forge.intermeta.de> (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> <20020329111833.B6490@work.bitmover.com>

Larry McVoy <lm@bitmover.com> writes:

>things back together for kernel developers.  What, exactly, did you
>hope to accomplish?

Awareness on your side that there are people presenting valid
arguments to you even if you don't agree. I did read the first posts
of the thread up until it degraded to "our application does every
integrity check possible to verify that the data is correct. So even
if it gets corrupted, we will know. That's why we better than the
rest" and you shot down everyone presenting you with other solutions
with this arguments. Well, in this case, you obviously knew that the
data is incorrect (because the disk died, I'm really feeling with you
here, from my eight IBM DTLA disks, three have died, too and I fear
that the remaining five will also die [1]) but all your checks
couldn't help you where just a few up-to-date backups would have.

Actually I'm a bit disappointed too, that you with all the
professionalism that you sprikle over this mailing list in every of
your posts, run such a showcase part of your business as bkbits.net on
IDE disks without RAID. And without clustering in case of emergency.

	Regards
		Henning


[1] I keep them in an dust free, climate controlled environment (18
degree centigrade all the time) and they're continously running (no
on-off operations) and they still die. IBM really deserves to suffer
for these disks. The last two died within six hours in the same box
after 20 months of continous running [2].

[2] I had the system up and running again 93 minutes after I pulled it
from the rack. Amanda and daily backups saved my ass. :-) And my
applications do not do integrity checks.

-- 
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 22:45 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
2002-03-29 22:44         ` Henning P. Schmiedehausen [this message]
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='a82qp6$ps3$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