From: Chris Mason <mason@suse.com>
To: Christian Mayrhuber <christian.mayrhuber@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: udpated data logging available
Date: 25 Jun 2003 15:15:29 -0400 [thread overview]
Message-ID: <1056568529.10097.135.camel@tiny.suse.com> (raw)
In-Reply-To: <200306231853.04098.christian.mayrhuber@gmx.net>
On Mon, 2003-06-23 at 12:53, Christian Mayrhuber wrote:
> This patch does better than reiserfs-jh-1, though It didn't eat the data on my system.
> I was unable to login as root (both tty and su) for about 2 minutes after system
> boot with the -1 patch (data=ordered mode and root fs on software raid1).
>
> 2.4.21 + data_logging and 2.4.21+data_logging + reiserfs-jh-2 + io-stalls-logging-6 does not
> show this behaviour.
>
> The quota patches seem to work with the experimental data logging stuff, too.
> The system latency is bad during heavy io, but this could hold true for all of the 2.4.x kernel series.
> You can try it yourself if you issue the command "dd if=/dev/zero of=tst bs=102400" in a shell and
> now try to start another app. (I did this to test the user quota.)
Thanks for giving things a try. I just uploaded io-stalls-7.diff, which
should do better at fixing latency during heavy io.
-chris
next prev parent reply other threads:[~2003-06-25 19:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 11:47 udpated data logging available Chris Mason
2003-06-18 13:56 ` Chris Mason
2003-06-23 2:45 ` Chris Mason
2003-06-23 16:53 ` Christian Mayrhuber
2003-06-25 19:15 ` Chris Mason [this message]
2003-06-26 0:16 ` Christian Mayrhuber
2003-06-26 1:47 ` Chris Mason
2003-06-26 11:42 ` Dieter Nützel
2003-06-26 12:53 ` Chris Mason
2003-06-26 13:36 ` Manuel Krause
2003-07-01 23:41 ` Manuel Krause
2003-07-02 1:44 ` Chris Mason
2003-06-26 17:19 ` Dieter Nützel
2003-07-02 0:46 ` Manuel Krause
2003-07-02 1:46 ` Chris Mason
2003-06-26 11:48 ` Dieter Nützel
2003-06-26 12:18 ` Philippe Gramoullé
2003-06-26 12:35 ` Dieter Nützel
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=1056568529.10097.135.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=christian.mayrhuber@gmx.net \
--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.