sshfs reports incorrect sizes on mountpoints

[GoogleCodeExporter]

sshfs reports incorrect sizes on mountpoints

[GoogleCodeExporter]

The 1,000 GB isn't coming from the Finder -- that's what sshfs reports. The 
sshfs implementation doesn't 
actually retrieve this information from the remote server. It just uses a 
hardcoded value of 1,000 GB. That part 
has nothing to do with MacFUSE.

As for "Zero KB free", you need to make sure:

1. That you indeed are running with the latest version of the kernel extension. 
Try the following at the 
command line:

kextstat | grep fuse

You should see 0.1.0b006 as the version. If you updated the binary tarball but 
you still see the old version, do 
the following:

sudo touch /System/Library/Extensions

Then reboot.

2. You need to mount using the '-oping_diskarb' option.

Original comment by [email protected] on 13 Jan 2007 at 2:27

[GoogleCodeExporter]

It is not reporting 0Kb free, it is reporting 0kb *used*.  To the end user, it 
is very confusing.

Original comment by [email protected] on 14 Jan 2007 at 9:53

[GoogleCodeExporter]

As I said earlier, the sshfs implementation lacks support for reporting the 
true storage numbers of the remote 
volume (directory, really -- and it's not that straightforward). If the end 
user is confused, they would be confused 
on any platform, not just MacFUSE/Mac OS X. If somebody wants to improve sshfs 
in this regard, look at 
sshfs_statfs() in sshfs.c.

Original comment by [email protected] on 14 Jan 2007 at 10:03

[GoogleCodeExporter]

Reported issue is a behavior of the sshfs implementation.

Original comment by [email protected] on 15 Jan 2007 at 9:35

• Changed state: WontFix