Re: [sshfs] inode problem when using git on a sshfs filesystem

From: Yann Droneaud <yann@droneaud.fr>
Date: Feb 17, 2011, 11:54 UTC
Message-ID: <7f02c4cb5ca13dae6de7caa1b6f90cfe.squirrel@webmail.ocsa-data.net>
In-Reply-To: <E1Pq1LW-0005rc-Qy@pomaz-ex.szeredi.hu>

Show 17 quoted lines

> 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