All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs blocks long on getdents64() during concurrent write
Date: Mon, 5 Aug 2002 15:04:36 +0400	[thread overview]
Message-ID: <20020805150436.A1176@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208051243430.31879-100000@pc40.e18.physik.tu-muenchen.de>

Hello!

On Mon, Aug 05, 2002 at 12:51:35PM +0200, Roland Kuhn wrote:

> > Unfortunatelly dirty flag for reiserfs gets set way to often than necessary,
> > we have some patches that should help this (from Chris Mason).
> > You can try these for yourself too, for example from here:
> > ftp://ftp.suse.com/pub/people/mason/patches/data-logging/02-commit_super-8-relocation.diff.gz 
> I will try it immediately. And I will try to find documentation on how 
> this all is working, so I can understand the implications. Does the 
> "flushing" also happen, when the journal is full? Or is it possible to 

Yes, if journal is full it is also flushed.

> begin a new journal while the old one is written out?

No, it is not possible to begin "new journal" in reiser3.

> > So you might try the patch I mentioned or you can mount with nodiratime mount
> > option to prevent updqting of directory atimes, but having atimes still to be
> > updated on regular files at the same time.
> Interesting mount option, though I think very few application actually use 
> atime anyway, isn't it?

I know for sure that atime on mbox-style files used to determine which messages
are new, and which are not. (N and O status in mutt).
There may be other users as well.

Bye,
    Oleg

  reply	other threads:[~2002-08-05 11:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 16:09 reiserfs blocks long on getdents64() during concurrent write Roland Kuhn
2002-08-05  5:44 ` Oleg Drokin
2002-08-05  9:22   ` Roland Kuhn
2002-08-05  9:54     ` Oleg Drokin
2002-08-05 10:51       ` Roland Kuhn
2002-08-05 11:04         ` Oleg Drokin [this message]
2002-08-05 18:19           ` Roland Kuhn
2002-08-05 18:30             ` Oleg Drokin
2002-08-05 18:54               ` Chris Mason
2002-08-05 19:48                 ` Roland Kuhn
2002-08-05 20:02                   ` Roland Kuhn
2002-08-05 22:14                     ` Chris Mason
2002-08-05 22:46                       ` Roland Kuhn
2002-08-06  0:47                         ` Chris Mason
2002-08-06 10:01                           ` Roland Kuhn
2002-08-05 19:11               ` Roland Kuhn

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=20020805150436.A1176@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuhn@e18.physik.tu-muenchen.de \
    /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.