From: "Yann Droneaud" <yann@droneaud.fr>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: "Yann Droneaud" <yann@droneaud.fr>,
fuse-sshfs@lists.sourceforge.net,
fuse-devel@lists.sourceforge.net, git@vger.kernel.org
Subject: Re: [sshfs] inode problem when using git on a sshfs filesystem
Date: Thu, 17 Feb 2011 12:54:43 +0100 [thread overview]
Message-ID: <7f02c4cb5ca13dae6de7caa1b6f90cfe.squirrel@webmail.ocsa-data.net> (raw)
In-Reply-To: <E1Pq1LW-0005rc-Qy@pomaz-ex.szeredi.hu>
> On Wed, 16 Feb 2011, Yann Droneaud wrote:
>> Hi,
>>
>> For some days, my usage of git is not as seamless as before.
>>
>> I'm using git along sshfs/fuse (don't blame me for that), and
>> each time I try to rebase one of my branch, I have a conflict when
>> applying
>> the third commit. Doing the same operation on a local filesystem works
>> without any problem.
>
> Yann, thanks for looking into this.
>
> Your findings are not surprising: unlike NFS, sshfs doesn't provide
> inode numbers and the fuse library also doesn't guarantee stable inode
> numbers by default.
>
But why does it have such behavior when trying to rmdir() a non empty
directory ?
> 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 ?)
BTW, the [no]forget option did not appears in sshfs --help output.
Regards.
--
Yann Droneaud
next prev parent reply other threads:[~2011-02-17 11:54 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 [this message]
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 ` [fuse-devel] " Goswin von Brederlow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7f02c4cb5ca13dae6de7caa1b6f90cfe.squirrel@webmail.ocsa-data.net \
--to=yann@droneaud.fr \
--cc=fuse-devel@lists.sourceforge.net \
--cc=fuse-sshfs@lists.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).