From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Patrick O'Rourke <porourke@egenera.com>,
Adrian Phillips <a.phillips@met.no>,
reiserfs-list@namesys.com
Subject: Re: rsync and memory leak on linux 2.2?
Date: Thu, 20 Feb 2003 09:19:23 +0300 [thread overview]
Message-ID: <20030220091923.A20036@namesys.com> (raw)
In-Reply-To: <3E5402B0.5030606@namesys.com>
Hello!
On Thu, Feb 20, 2003 at 01:18:24AM +0300, Hans Reiser wrote:
> Thanks Patrick. This leaves us with one unsolved reiserfs V3 bug that I
> know of (unlink related one, vs is working on it, and he is not
Vladimir tracked that down yesterday.
At least we think so. (and even if the fix we discussed yesterday won't help,
that'd mean we have another bug in addition to what Vladimir found.
And this is indeed a race between two iget(). I am not sure if VFS
is flawed, but I think at least partially it is. Because in 2.5
that piece of code redesigned right way.)
> completely sure it is reiserfs not vfs....). Oleg, am I right in
> thinking that the samba+reiserfs bug looks like a samba bug?
That turned out to be fs corruption of unknown source. Hardware is
the main suspect for now.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-20 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 17:11 rsync and memory leak on linux 2.2? Patrick O'Rourke
2003-02-13 19:15 ` Oleg Drokin
2003-02-14 6:38 ` Adrian Phillips
2003-02-14 10:01 ` Oleg Drokin
2003-02-14 10:09 ` Adrian Phillips
2003-02-19 21:24 ` Patrick O'Rourke
2003-02-19 22:18 ` Hans Reiser
2003-02-20 6:19 ` Oleg Drokin [this message]
2003-02-14 14:04 ` Patrick O'Rourke
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=20030220091923.A20036@namesys.com \
--to=green@namesys.com \
--cc=a.phillips@met.no \
--cc=porourke@egenera.com \
--cc=reiser@namesys.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.