All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Jakob Oestergaard <jakob@unthought.net>, linux-kernel@vger.kernel.org
Subject: Re: ReiserFS buglet
Date: Tue, 24 Sep 2002 15:35:40 +0400	[thread overview]
Message-ID: <20020924153540.A25934@namesys.com> (raw)
In-Reply-To: <3D904CC2.4080607@namesys.com>

Hello!

On Tue, Sep 24, 2002 at 03:30:10PM +0400, Hans Reiser wrote:

> >>It's a question of which errors one wishes to handle, and which you
> >>simply choose to ignore.
> >Yes, that's true. Reiserfs chose to not handle any HW errors, this is even
> >written somewhere in our FAQ.
> No, this is not true.  We handle IO errors.  We do not attempt to handle 

Ok, IO errors is not kind of HW errors I meant.
I meant broken HW that does not behave like it should behave according
to specs (i.e. writing other data than we asked it, damaging memory
content and stuff).

> every imaginable hardware error because no one can.  If your CPU 
> overheats, our code makes no effort to compensate for it.

Bye,
    Oleg

      reply	other threads:[~2002-09-24 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  7:24 ReiserFS buglet Jakob Oestergaard
2002-09-24  9:21 ` Oleg Drokin
2002-09-24  9:27   ` Jakob Oestergaard
2002-09-24  9:42     ` Hans Reiser
2002-09-24  9:47       ` Jakob Oestergaard
2002-09-24  9:48     ` Oleg Drokin
2002-09-24 10:03       ` Jakob Oestergaard
2002-09-24 10:25         ` Oleg Drokin
2002-09-24 10:39           ` Jakob Oestergaard
2002-09-24 10:54             ` Oleg Drokin
2002-09-24 11:30           ` Hans Reiser
2002-09-24 11:35             ` Oleg Drokin [this message]

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=20020924153540.A25934@namesys.com \
    --to=green@namesys.com \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.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.