From: Hans Reiser <reiser@namesys.com>
To: Joe Feise <jfeise@feise.com>, vs <vs@thebsh.namesys.com>
Cc: Jonathan Briggs <jbriggs@esoft.com>, reiserfs-list@namesys.com
Subject: Re: Reiser4 crash 2.6.16-mm1
Date: Tue, 28 Mar 2006 13:04:38 -0800 [thread overview]
Message-ID: <4429A4E6.5000202@namesys.com> (raw)
In-Reply-To: <20060328205021.3873.qmail@pv105234.reshsg.uci.edu>
Joe Feise wrote:
> Jonathan Briggs writes:
>
>> 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
>
>
> Indeed, it does. Dell gets that right on server machines, at least...
> I have now recreated the fs on that partition, and played the data
> back from backup, and it works fine. I have made a copy of the old
> partition with dd, to be able to run some more tests when I have time.
> -Joe
>
>
Well, if it is ECC RAM, then we should probably assume it is a bug.
Sigh. Vs, can you look at it?
next prev parent reply other threads:[~2006-03-28 21:04 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
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 [this message]
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=4429A4E6.5000202@namesys.com \
--to=reiser@namesys.com \
--cc=jbriggs@esoft.com \
--cc=jfeise@feise.com \
--cc=reiserfs-list@namesys.com \
--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.