Re: FSAllocateFork
Re: FSAllocateFork
- Subject: Re: FSAllocateFork
- From: John Stiles <email@hidden>
- Date: Sat, 07 Oct 2006 14:10:24 -0700
With a modern AFP server, you can store very large files without issues.
(10GB+ in my experience.)
Is the file server a Mac OS X machine or a Windows machine?
Rosyna wrote:
This is likely due to the fact you cannot have a larger than 2gig file
on these formats.
On Mac OS X 10.4 or later, you can use FSCopyObjectSync() instead of
the sample code. FSAllocateFork() is for preallocating space on
volumes formats that support it. This can speed up the write. For AFP
volumes, I'm not sure if it matters.
Ack, at 10/6/06, Lorenzo said:
I copy a file to a remote AFP disk using the routines from
FSCopyObject.c.
When the file is > 2GB the API FSAllocateFork always returns an error
-34
(disk full) even if the AFP remote disk has 4 GB free space.
So as I have read on the web, I have omitted FSAllocateFork .
It seems to work ok even with old MacOS 9 files with resource forks.
Do you think this omission could cause some problem?
I check the destination disk space using the new Cocoa APIs.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden