All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jonathan Briggs <jbriggs@esoft.com>
Cc: jfeise@ics.uci.edu, Toby Thain <toby@smartgames.ca>,
	reiserfs-list@namesys.com, vs <vs@thebsh.namesys.com>
Subject: Re: Reiser4 crash 2.6.16-mm1
Date: Tue, 28 Mar 2006 12:08:57 -0800	[thread overview]
Message-ID: <442997D9.7000505@namesys.com> (raw)
In-Reply-To: <1143573487.2380.1.camel@localhost>

Jonathan Briggs wrote:

>On Tue, 2006-03-28 at 07:34 -0800, Joachim Feise wrote:
>[...]
>  
>
>>This is a production machine that I can't take offline for too long.
>>But yes, I have compiled the kernel on another reiser4 partition over night,
>>without problems.
>>If this was a memory problem, it would indeed manifest itself in other areas
>>with more or less random errors. The fact that it does not indicates to me that
>>this is a fs problem. So, at this point I am ruling out a memory issue.
>>    
>>
>
>And if it's a production machine, it is using ECC RAM, I would hope.  If
>it is, memory problems (unreported ones, anyway) are very, very
>unlikely.
>  
>
Jonathan, be merciful, ECC ram last I checked is twice the cost of
regular and the mobs cost more too.  (I am sure the cost to produce is <
15% more, which makes it a great pity Intel does not standardize on
requiring it and force it to be cheap)  Some folks need to save money. 
Yeah, I know, this time it may have cost him more in cost of his time
but we are all just assuming it is memory.  Unfortunately, unless he
checks it or we see an identical error message from another user with
checked memory, or vs tells me he sees a flaw in the code, we need to
assume it is memory.

Reiser4 is more stable than the hardware it runs on.  At some point it
will be more stable than the hardware users are sure isn't the problem,
like V3 became.;-)

Hans

  reply	other threads:[~2006-03-28 20:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 21:41 Reiser4 crash 2.6.16-mm1 Joe Feise
2006-03-27 21:58 ` Toby Thain
2006-03-27 22:32   ` Joe Feise
2006-03-28  4:39     ` Valdis.Kletnieks
2006-03-28  6:34       ` Toby Thain
2006-03-28 15:34         ` Joachim Feise
2006-03-28 16:49           ` Toby Thain
2006-03-28 19:18           ` Jonathan Briggs
2006-03-28 20:08             ` Hans Reiser [this message]
2006-03-28 20:45               ` Jonathan Briggs
2006-03-28 21:22                 ` Gregory Maxwell
2006-03-28 21:56                   ` Joe Feise
2006-03-28 20:54               ` Joe Feise
2006-03-28 21:52                 ` Sergey Ivanov
2006-03-28 22:03                   ` Joe Feise
2006-03-28 20:50             ` Joe Feise
2006-03-28 21:04               ` Hans Reiser
2006-03-28  3:47 ` Joe Feise

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=442997D9.7000505@namesys.com \
    --to=reiser@namesys.com \
    --cc=jbriggs@esoft.com \
    --cc=jfeise@ics.uci.edu \
    --cc=reiserfs-list@namesys.com \
    --cc=toby@smartgames.ca \
    --cc=vs@thebsh.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.