From: Hans Reiser <reiser@namesys.com>
To: Patrick O'Rourke <porourke@egenera.com>
Cc: Oleg Drokin <green@namesys.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 01:18:24 +0300 [thread overview]
Message-ID: <3E5402B0.5030606@namesys.com> (raw)
In-Reply-To: <1045689849.1168.24.camel@barnes>
Patrick O'Rourke wrote:
>On Fri, 2003-02-14 at 05:01, Oleg Drokin wrote:
>
>
>
>>On Fri, Feb 14, 2003 at 07:38:41AM +0100, Adrian Phillips wrote:
>>
>>
>>> Patrick> We have two machines running Linux 2.2 with ReiserFS
>>> Patrick> v3.5.32 and we're seeing a memory leak which we feel is
>>> Patrick> related to reiser and some interaction with rsync.
>>>Well, there is a 3.5.34 which has, obviously, a number of bug
>>>
>>>
>
>I just thought I would follow up with a note that the bug turned
>out NOT to be in the reiser code. The rsync operation I described
>turned out to be a red herring.
>
>Thanks for the suggestions,
>
>Pat
>
>
>
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
completely sure it is reiserfs not vfs....). Oleg, am I right in
thinking that the samba+reiserfs bug looks like a samba bug?
--
Hans
next prev parent reply other threads:[~2003-02-19 22:18 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 [this message]
2003-02-20 6:19 ` Oleg Drokin
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=3E5402B0.5030606@namesys.com \
--to=reiser@namesys.com \
--cc=a.phillips@met.no \
--cc=green@namesys.com \
--cc=porourke@egenera.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.