From: Goswin von Brederlow <goswin-v-b@web.de>
To: "Yann Droneaud" <yann@droneaud.fr>
Cc: "Miklos Szeredi" <miklos@szeredi.hu>,
fuse-devel@lists.sourceforge.net,
fuse-sshfs@lists.sourceforge.net, git@vger.kernel.org
Subject: Re: [fuse-devel] [sshfs] inode problem when using git on a sshfs filesystem
Date: Fri, 18 Feb 2011 08:41:16 +0100 [thread overview]
Message-ID: <87ei75ssbn.fsf@frosties.localnet> (raw)
In-Reply-To: <7f02c4cb5ca13dae6de7caa1b6f90cfe.squirrel@webmail.ocsa-data.net> (Yann Droneaud's message of "Thu, 17 Feb 2011 12:54:43 +0100")
"Yann Droneaud" <yann@droneaud.fr> writes:
>> On Wed, 16 Feb 2011, Yann Droneaud wrote:
>> Fuse version 2.8.x has a "noforget" option that should provide stable
>> inode numbers, at the cost of unbounded memory use. Could you please
>> try if this option fixes these issues?
>>
>
> Yes, this option seems to fix the problem.
>
> I will try it for a while to see if this is stable enough for a full day
> of git working. (How can I check memory usage ?)
The memory usage comes from the inodes. Fuse will never forget an inode
(unless you delete the dile/dir) that was once visited (thereby giving
allways the same inode number). As long as you don't have a billion
files that generally doesn't matter.
MfG
Goswin
next prev parent reply other threads:[~2011-02-18 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 22:04 inode problem when using git on a sshfs filesystem Yann Droneaud
2011-02-17 8:37 ` Michael J Gruber
[not found] ` <1297893854.4097.43.camel-vNW8ozRvgWupuGC+iAP0z+TW4wlIGRCZ@public.gmane.org>
2011-02-17 10:44 ` [sshfs] " Miklos Szeredi
2011-02-17 11:54 ` Yann Droneaud
2011-02-17 13:08 ` Miklos Szeredi
2011-02-17 18:11 ` Yann Droneaud
2011-02-17 19:59 ` Miklos Szeredi
2011-02-18 7:41 ` Goswin von Brederlow [this message]
2011-02-17 12:05 ` Yann Droneaud
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=87ei75ssbn.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=fuse-devel@lists.sourceforge.net \
--cc=fuse-sshfs@lists.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=yann@droneaud.fr \
/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.