From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: Chris Mason <mason@suse.com>, Oleg Drokin <green@namesys.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH] finally... data logging for 2.4.20-pre10
Date: Fri, 18 Oct 2002 15:41:00 +0200 [thread overview]
Message-ID: <3DB00F6C.6060609@mb.tu-ilmenau.de> (raw)
In-Reply-To: 1034709883.5053.920.camel@tiny
On 10/15/2002 09:24 PM, Chris Mason wrote:
> Hello all,
>
> I've uploaded new data logging code against 2.4.20-pre10 to
>
> ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20
>
> The mirror might take a little while to update.
>
> This code is lightly tested, use with caution for a few days. The
> journal relocation patches are not complete yet, I haven't integrated
> them with the new options parsing code in 2.4.20-pre, so you can't pass
> -o jdev= when mounting the FS.
>
> Aside from merging into the latest kernel, there are a few bug fixes for
> corner case oopsen hit during suse testing.
>
> -chris
>
Hi !
Yesterday I added the 2.4.20-pre10 data-logging test results to
http://manuel.krause.bei.t-online.de/topics/sw-tests.2.htm
The data-logging tests were performed in data=ordered mode. For all
these tests disk content remained the same.
Somehow 2.4.19-final was faster than everything that followed...
Best regards,
Manuel
next prev parent reply other threads:[~2002-10-18 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 19:24 [PATCH] finally... data logging for 2.4.20-pre10 Chris Mason
2002-10-15 22:16 ` Manuel Krause
2002-10-18 13:41 ` Manuel Krause [this message]
2002-10-23 19:01 ` John Dalbec
2002-10-23 21:59 ` Manuel Krause
2002-10-24 12:51 ` John Dalbec
2002-10-24 13:12 ` Chris Mason
2002-11-12 15:39 ` Toby Dickenson
2002-11-18 14:31 ` John Dalbec
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 22:29 JP Howard
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=3DB00F6C.6060609@mb.tu-ilmenau.de \
--to=manuel.krause@mb.tu-ilmenau.de \
--cc=green@namesys.com \
--cc=mason@suse.com \
--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.