From: Joachim Feise <jfeise@ics.uci.edu>
To: Toby Thain <toby@smartgames.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 crash 2.6.16-mm1
Date: Tue, 28 Mar 2006 07:34:20 -0800 [thread overview]
Message-ID: <4429577C.7020105@ics.uci.edu> (raw)
In-Reply-To: <F01E6B3F-3EBE-4982-9978-C79554F01FDA@smartgames.ca>
Toby Thain wrote on 03/27/06 22:34:
> On 27-Mar-06, at 11:39 PM, Valdis.Kletnieks@vt.edu wrote:
>
>> On Mon, 27 Mar 2006 14:32:14 PST, Joe Feise said:
>>
>>> Thanks for the suggestion. I haven't run a memtest, but I don't
>>> really think
>>> that the memory is bad. The machine most likely would have had
>>> other issues
>>> if that was the case.
>> You'd be *amazed*. Intermittently weak memory (especially if it's
>> just one bad
>> bit) can manifest in the most odd ways.
>
>
> I tend to agree. I spent weeks/months chasing down what I thought was
> a chipset bug, when it was bad RAM. Disk reads (and probably writes)
> were being corrupted and the kernel did not know about it. Was very
> frustrating ... until I figured out the real problem.
>
> Joe, did you soak the test at least overnight? Have you done any
> heavy compiles (like building X11, or gcc) lately? Compilers are
> often the canaries in the mine, when it comes to RAM. I'm not saying
> this is your problem but it would be good to rule out first.
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.
-Joe
next prev parent reply other threads:[~2006-03-28 15:34 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 [this message]
2006-03-28 16:49 ` Toby Thain
2006-03-28 19:18 ` Jonathan Briggs
2006-03-28 20:08 ` Hans Reiser
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=4429577C.7020105@ics.uci.edu \
--to=jfeise@ics.uci.edu \
--cc=reiserfs-list@namesys.com \
--cc=toby@smartgames.ca \
/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.