sshfs reports incorrect sizes on mountpoints

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Build and install fuse-binaries-0.1.0b006
2. Build and install sshfs
3. Mount file share, it incorrectly reports zero Kb, with 1,000 GB free

What is the expected output? What do you see instead?
Size is 250G for drive, it reflects 1,000GB free incorrectly

What version of the product are you using? On what operating system?
0.1.0b006, 8.8.2 Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; 
root:xnu-792.14.14.obj~1/RELEASE_I386 i386 i386

Please provide any additional information below.

Attached debug log

Original issue reported on code.google.com by rave...@gmail.com on 12 Jan 2007 at 10:48

Attachments:

• sshfs.log

[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 si...@gmail.com 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 rave...@gmail.com 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 si...@gmail.com on 14 Jan 2007 at 10:03

[GoogleCodeExporter]

Reported issue is a behavior of the sshfs implementation.

Original comment by si...@gmail.com on 15 Jan 2007 at 9:35

• Changed state: WontFix