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 22:30:16 +0400 [thread overview]
Message-ID: <20020805223016.A14603@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208052014220.31879-100000@pc40.e18.physik.tu-muenchen.de>
Hello!
On Mon, Aug 05, 2002 at 08:19:05PM +0200, Roland Kuhn wrote:
> > > > ftp://ftp.suse.com/pub/people/mason/patches/data-logging/02-commit_super-8-relocation.diff.gz
> >From there I get 'permission denied', but I got it somewhere else (google
> is great).
> However, it does not apply cleanly to 2.4.19. It is already partly in, as
> it seems, but there are some rejects that are not obvious to fix for me.
> If this patch still makes sense, it would be great if someone with more
> knowledge/experience than me could have a look...
In the same dir there is
03-data-logging-24.diff.gz
It contains this patch and more stuff, you can try it.
> > No, it is not possible to begin "new journal" in reiser3.
> Is this going to change in reiser4?
Sort of, there would be no static journal.
Bye,
Oleg
next prev parent reply other threads:[~2002-08-05 18:26 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
2002-08-05 18:19 ` Roland Kuhn
2002-08-05 18:30 ` Oleg Drokin [this message]
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=20020805223016.A14603@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.