All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH CFT] tons of logging patches
Date: 08 Jul 2002 09:51:33 -0400	[thread overview]
Message-ID: <1026136293.5663.56.camel@tiny> (raw)
In-Reply-To: <3D2396AF.8020508@mb.tu-ilmenau.de>

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.

> 
> Can you, please, answer my old questions as of:
> 
> On 06/25/2002 02:55 AM, Manuel Krause mainly wrote (but too much more):
> 
>  > Is the rootflag needed any more? Does your patchset work with all
>  > pending ReiserFS patches together, now?

Yes, you still need the rootflag.  I haven't tried to merge it with all
the namesys pending patches, except for the journal relocation stuff and
the commit_super speedups.
 
> 
> Thanks,
> 
> I don't get a performance decrease with "13", and: Is it really 
> dangerous to use "13" in this mode of operation?

It is dangerous to use -13 at all, although the bug is pretty difficult
to trigger.  Please run reiserfsck --check before upgrading.

-chris



  reply	other threads:[~2002-07-08 13:51 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  3:51 [PATCH CFT] tons of logging patches Chris Mason
2002-06-03  4:04 ` Chris Mason
2002-06-03  8:46 ` Matthias Andree
2002-06-03 12:26   ` Chris Mason
2002-06-04  0:45 ` Manuel Krause
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-05 21:32             ` Chris Mason
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
2002-07-02 18:16                         ` Chris Mason
2002-07-03 20:56                           ` Chris Mason
2002-07-04  0:28                             ` Manuel Krause
2002-07-08 13:51                               ` Chris Mason [this message]
2002-07-09  0:22                                 ` [PATCH CFT] tons of logging patches + addon Manuel Krause
2002-06-04  2:57   ` [PATCH CFT] tons of logging patches Chris Mason
2002-06-04  4:16     ` Manuel Krause
2002-06-04 13:34       ` Chris Mason
2002-06-04 21:20         ` Hans Reiser
2002-06-05  0:16           ` Robert Brockway
2002-06-05  8:43           ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 15:48 berthiaume_wayne
2002-06-04 16:55 ` Chris Mason
2002-06-22 20:02 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-14  0:52 Manuel Krause
2002-08-02 12:28 ` 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=1026136293.5663.56.camel@tiny \
    --to=mason@suse.com \
    --cc=manuel.krause@mb.tu-ilmenau.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.