From: Chris Mason <mason@suse.com>
To: Chris Mason <mason@suse.com>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"ReiserFS List" <reiserfs-list@namesys.com>
Subject: Re: Re: [PATCH CFT] tons of logging patches
Date: 12 Jul 2002 15:43:11 -0400 [thread overview]
Message-ID: <1026502991.4952.136.camel@tiny> (raw)
In-Reply-To: <1026223243.5603.124.camel@tiny>
On Tue, 2002-07-09 at 10:00, Chris Mason wrote:
> On Tue, 2002-07-09 at 09:52, Dieter Nützel wrote:
> > On Monday, 8 July 2002 13:51, Chris Mason wrote:
> > > On Wed, 2002-07-03 at 20:28, Manuel Krause wrote:
> > >
> > > > So far the 13 prerelease works fine under rootflags boot and
> > > > mount/remount option "data=ordered" on here.
> > >
> > > I think I've got the bug, it was newly introduced in -13. New stuff
> > > will be uploaded today.
> > >
> Sigh, further testing showed I'd only fixed half of the bug. The other
> half is somewhere deep writepage/truncate interaction. I'm still trying
> to find it.
Well, after a week of fixing minor things and adding debugging code,
this bug still goes unsolved. The only good news is that I can also
trigger it on pure 2.4.19-rc1 and ext2. The bug seems to either be in
the VM or my ram, so I'm having a little memtest86 party overnight.
I've uploaded 03-beta-data-logging-16, it should be more stable and
faster than -11 and -13 were, but includes more debugging checks to try
and make sure I'm not screwing things up. You can grab the patches at:
ftp://ftp.suse.com/pub/people/mason/patches/data-logging
If anyone wants to try and reproduce my memory corruption bug (can and
probably will lead to FS corruption), just let 10 fsx processes run in a
loop for ~3 hours or so on an SMP machine.
-chris
next prev parent reply other threads:[~2002-07-12 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 20:02 [PATCH CFT] tons of logging patches Dieter Nützel
2002-06-24 19:05 ` Chris Mason
2002-07-09 13:52 ` Dieter Nützel
2002-07-09 14:00 ` Chris Mason
2002-07-12 19:43 ` Chris Mason [this message]
2002-07-14 0:52 ` Manuel Krause
2002-08-02 12:28 ` Chris Mason
2002-08-02 12:34 ` Chris Mason
2002-08-02 12:59 ` Hans Reiser
2002-08-02 13:10 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 3:51 Chris Mason
2002-06-04 1:49 ` Manuel Krause
2002-06-04 2:20 ` Chris Mason
2002-06-04 3:28 ` Manuel Krause
2002-06-04 13:12 ` Chris Mason
2002-06-05 21:13 ` Manuel Krause
2002-06-05 21:27 ` Manuel Krause
2002-06-06 0:09 ` Chris Mason
2002-06-06 4:59 ` Manuel Krause
2002-06-12 22:32 ` Manuel Krause
2002-06-17 0:47 ` Chris Mason
2002-06-17 0:31 ` Manuel Krause
2002-06-17 19:04 ` Chris Mason
2002-06-21 0:25 ` Chris Mason
2002-06-25 0:55 ` Manuel Krause
2002-06-28 13:51 ` Chris Mason
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=1026502991.4952.136.camel@tiny \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--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.