From: Alex Zarochentsev <zam@namesys.com>
To: Jake Maciejewski <maciejej@msoe.edu>
Cc: Isaac Chanin <chanin@WPI.EDU>, reiserfs-list@namesys.com
Subject: Re: AMD64 progress?
Date: Tue, 8 Feb 2005 22:12:58 +0300 [thread overview]
Message-ID: <20050208191258.GF7482@backtop.namesys.com> (raw)
In-Reply-To: <1107887159.12393.6.camel@gentoo>
On Tue, Feb 08, 2005 at 12:25:58PM -0600, Jake Maciejewski wrote:
> On Mon, 2005-02-07 at 22:51 +0300, Alex Zarochentsev wrote:
> > On Mon, Feb 07, 2005 at 01:34:56PM -0600, Jake Maciejewski wrote:
> > > I'm running reiser4progs 1.0.3 and 2.6.10 patched with reiser4 from
> > > 2.6.11-rc3-mm1 (and this patch).
> > >
> > > I've been doing the simultaneous dd and kernel compilation that has
> > > always crashed reiser4 on AMD64 in the past. After about an hour with
> > > debugging and two hours without debugging, I'm thinking of more ways to
> > > torture the FS. For now it looks like reiser4 is working on AMD64!
> >
> > i think so. reiser4/amd64 passed 5h of stress testing instead of crashing in
> > first 30min.
> >
> Have you been stress testing with debugging disabled? I was doing some
> extreme testing and crashed reiser4 with this patch twice. The same test
how it crashed? Was the fs corrupted after the crash?
> that crashed it one of the times passes on reiserfs (didn't try the
> other), and if enable debugging, I can torture reiser4 all night and
> still not crash it. I'll do some more tests and try to identify a
> simple, reproducible crash scenario.
Thanks,
Alex.
next prev parent reply other threads:[~2005-02-08 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 5:33 AMD64 progress? Jake Maciejewski
2005-01-14 0:03 ` David Masover
2005-01-14 20:17 ` Alex Zarochentsev
2005-01-14 22:58 ` Jake Maciejewski
2005-01-16 2:26 ` Isaac Chanin
2005-02-07 13:29 ` Alex Zarochentsev
2005-02-07 19:34 ` Jake Maciejewski
2005-02-07 19:51 ` Alex Zarochentsev
2005-02-08 18:25 ` Jake Maciejewski
2005-02-08 19:12 ` Alex Zarochentsev [this message]
2005-02-08 20:49 ` Jake Maciejewski
2005-02-08 20:29 ` Isaac Chanin
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=20050208191258.GF7482@backtop.namesys.com \
--to=zam@namesys.com \
--cc=chanin@WPI.EDU \
--cc=maciejej@msoe.edu \
--cc=reiserfs-list@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.