sftp doesn't have statfs()-like functionality, so sshfs can't really know the "size" (and space available) of the remote "disk". So, it has too cook something up. That's why you see 1000GB (cooked up size).
The Zero KB thing is a problem though. I've seen it myself recently. Looks like an issue with the Finder and/or Desktop Services in Mac OS X. It may be possible to do something in MacFUSE to fix it (well, not fix Finder's issue, but make the Finder not run into this issue). I'll probably do it in the next MacFUSE release. Meanwhile, if you're up to compiling the MacFUSE kernel extension from source, you can try the following. In core/10.5/fusefs/fuse_vfsops.c, you'll see an instance of: ... // | VOL_CAP_FMT_FAST_STATFS ... Just uncomment this line and recompile. See if it stops showing Zero KB available in the Finder. Amit On Feb 5, 11:24 am, nghtstr <[EMAIL PROTECTED]> wrote: > Ok, first I am using the standard 1.3.1 Core for Leopard. I am also > running MacFusion, which gives me easy access to mount a SSH > connection. However, this is the strange part, sometimes it shows as > available space as Zero KB, and other times 1,000 GB available. I am > certain that there must be some sort of flag or something that I can > set which will allow me to get the right space available, but mainly I > just need it to stop showing Zero KB available. > > I appreciate all of the help you can give, and I think that this > project is one of the best I have ever seen. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
