40 MB Filemaker file freezes while saving, 5 MB does not

[GoogleCodeExporter]

What steps will reproduce the problem?
1.dragging a Filemaker file to a remote macFuse volume 
2.it seems that a certain file size must be exceeded
3.

What is the expected output? What do you see instead?

The expected output would be a complete file on the server that can be 
copied back and it would work the same as original.
Instead the copying process halts at about 95% and then times out.
The file that is produced that way is unusable.

If I use a "clone", that is an empty database of the same kind, 
without any records, it works as expected: I can copy back the file 
from the server and it is usable like the original.

What version of the product are you using? On what operating system?

MacFuse 1.2 Beta 3 /  I could not get 1.7 to work yet. The 
installation process is performed without reported error, but there is 
no handle to start the MacFuse program

Os 10.4.11 with Classic environment and Filemaker V 5.0 Dv 3

Please provide any additional information below.

Original issue reported on code.google.com by wi...@gmx.de on 21 Aug 2008 at 10:31

[GoogleCodeExporter]

Please see my response to your previous report of this: 
http://code.google.com/p/macfuse/issues/detail?id=372

There is no "MacFuse 1.2 Beta 3". There is no "MacFuse program" that you need 
to "run". MacFUSE is not a "remote" file 
system. (You can write remote file systems using MacFUSE as a building block 
though.)

I think you are talking about this:

http://groups.google.com/group/MacFusion-devel

If so, you should report issues on that web site. MacFusion requires MacFUSE, 
but is otherwise an entirely different project.

Original comment by si...@gmail.com on 21 Aug 2008 at 10:52

• Changed state: Invalid

[GoogleCodeExporter]

Yes, you are right

I was a bit confused about MacFuse and MacFusion and see a bit clearer now. And 
even the "Issue" got solved in a way: The big file needs longer housekeeping 
procedures at the end of copying so the timeout is issued. If I just let him 
"retry", it works as expected

Thank you for mentioning the proper address to report this timeout problem.

And thank you for for delivering this great feature to the MacOs, so we can use 
remote servers just the same as a volume within the computer itself: this is 
how it should be!

WiLi

Original comment by wi...@gmx.de on 21 Aug 2008 at 11:55

[GoogleCodeExporter]

> I was a bit confused about MacFuse and MacFusion and see a bit clearer now. 
And 
> even the "Issue" got solved in a way: The big file needs longer housekeeping 
> procedures at the end of copying so the timeout is issued. If I just let him 
> "retry", it works as expected

On Leopard, there's no timeout dialog. (Mainly because the kernel interface 
needed to display that dialog is 
deprecated in Leopard.) So, on Leopard, MacFUSE will have no choice but to 
unceremoniously eject any 
volume upon timeout. Jarring as it may sound, this is to protect the system 
from locking up.

If you know that the file system you are mounting will be performing operations 
that outlast the timeout, you 
can use a custom value for the timeout. It's the daemon_timeout mount-time 
option. The value you specify 
represents the timeout in seconds.

Original comment by si...@gmail.com on 22 Aug 2008 at 12:14

[GoogleCodeExporter]

No, I do not use Leopard, since my computer is a G3 iBook. I use 10.4.11 . It 
is a 
pity that many programs and system additions are not continued for the G3. Is 
it not 
a computer anymore?

Also MacFusion in the newer release is for Leopard only.

I am a bit uncertain now whether I have a possibility to change the timeout 
value in 
Tiger and would be happy if can advise further.

Thank you

WiLi

Original comment by wi...@gmx.de on 22 Aug 2008 at 7:39