[sshfs] Certain servers report 0 bytes available.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. sshfs user@server.com: /Volumes/disk
2. in Finder, open /Volumes/disk

What is the expected output? What do you see instead?
I expect see a non-zero number of bytes remaining. I expect to be able to 
duplicate files and 
copy files to the server. Instead, I see Zero KB available and am unable to 
copy or duplicate files.

What version of the product are you using? On what operating system?
SSHFS version 1.7
FUSE library version: 2.6.1
FUSE kernel interface version 7.8
fuse-0.1.0b004
Mac OS X Server 10.4.8 (8L127), Power Mac G5, PowerMac7,2

Please provide any additional information below.
This doesn't happen on all servers. Only one of the ones I use regularly has 
this problem. 
Another works fine, and reports 1000GB available. According to df -h, 1000GB 
are available on 
this server as well, but the Finder reports Zero KB available.

I can make an account on the server if you would like to test it, just let me 
know.

Original issue reported on code.google.com by devin.l...@gmail.com on 12 Jan 2007 at 6:57

[GoogleCodeExporter]

It's a Finder thing. You'll see that things work fine from the command line 
still.

The issue is that the Finder is checking the newly mounted volume before the 
sshfs daemon has had a chance 
to tell the kernel that it's ready. Until the kernel gets this notification 
from the daemon, MacFUSE doesn't know 
what the space available etc. is. However, it still needs to report something, 
because, if the daemon never 
replied or crashed, MacFUSE still has to be able to let you unmount things 
gracefully. So, MacFUSE does a 
simple thing: it reports that there's zero space available. Unfortunately, the 
Finder latches onto this 
information for good, even though a moment later MacFUSE has the correct 
information and it does report the 
correct information thereafter.

I've known about this issue for a while and I had several solutions in mind, 
none of which made it to the 
binary I created. Since many people seem to be running into this, I've added a 
simple solution (diff 
fuse_vfsops.c for details) and updated the binary.

Please try fuse-0.1.0b005 and see if the problem goes away. Also, if you want 
the Finder to behave nicely with 
MacFUSE file systems, you should use the ping_diskarb option while mounting. 
For example:

sshfs user@server.com: /Volumes/disk -oping_diskarb

Original comment by si...@gmail.com on 12 Jan 2007 at 7:29

• Changed state: Fixed

[GoogleCodeExporter]

I can't even get sshfs to work with b005.

When I use sshfs user@server.com /Volumes/disk, I get "fusefs file system is 
not available."
When I try to manually load the kernel extension, I get "kextload: extension 
/System/Library/Extensions/
fusefs.kext is not authentic" and the extension does not show up in kextstat.

I copied the new files over the old ones using rsync -ru --links System /System 
and rsync -ru --links usr/
local /usr/local as I did with b004.

I'll try rebooting again (unloading the b004 kext caused a kp, so perhaps that 
borked the restart) and report 
back in a minute.

Original comment by devin.l...@gmail.com on 12 Jan 2007 at 8:41

[GoogleCodeExporter]

After a fresh reboot I get the same problem.

Original comment by devin.l...@gmail.com on 12 Jan 2007 at 8:44

[GoogleCodeExporter]

Before you reboot, try doing the following:

{{{
$ sudo touch /System/Library/Extensions
}}}

Original comment by si...@gmail.com on 12 Jan 2007 at 6:26

[GoogleCodeExporter]

Before you reboot, try doing the following:

{{{
$ sudo touch /System/Library/Extensions
}}}

Original comment by si...@gmail.com on 12 Jan 2007 at 6:27

[GoogleCodeExporter]

Please ignore the duplicate message. You should also ignore the "{{{" and "}}}" 
... I thought this thing takes Wiki 
syntax.

Original comment by si...@gmail.com on 12 Jan 2007 at 6:36

[GoogleCodeExporter]

Aha, that fixes it. I can load b006 fine now, and tried the -oping_diskarb 
option as you suggested, but I still get 
the same problem (Zero bytes available).

Original comment by devin.l...@gmail.com on 12 Jan 2007 at 6:56

[GoogleCodeExporter]

That is, the first time it didn't work. When I tried again later I got 1000GB 
free and was able to add files to the 
server.

Original comment by devin.l...@gmail.com on 12 Jan 2007 at 10:42