• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FSAllocateFork
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSAllocateFork


  • Subject: Re: FSAllocateFork
  • From: Lorenzo <email@hidden>
  • Date: Sat, 07 Oct 2006 23:33:27 +0200

The server could be a MacOS X volume, a Windows volume, a WebDave volume,
... any kind of volume as well as the Finder can copy files to.
I am going to try the API FSCopyObjectSync() and verify whether it can fix
my needs. Thank you for the suggestion.

Anyway, after talking with some colleaugue, I suppose that the API
FSAllocateFork has really a bug since it fails to detect the right
destination disk free space in case of copying files larger than 2GB. It
always returns error -34 (disk full) even when the disk has indeed free
enough free space to copy the file to.


Best Regards
--
Lorenzo
email: email@hidden

> From: John Stiles <email@hidden>
> Date: Sat, 07 Oct 2006 14:10:24 -0700
> To: Rosyna <email@hidden>
> Cc: Lorenzo <email@hidden>, email@hidden
> Subject: Re: FSAllocateFork
>
> 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

  • Follow-Ups:
    • Re: FSAllocateFork
      • From: Bill Bumgarner <email@hidden>
References: 
 >Re: FSAllocateFork (From: John Stiles <email@hidden>)

  • Prev by Date: Re: NSArrayController vs. fetch
  • Next by Date: Re: WhackedTV - ISO C++ forbids declaration of 'SeqGrabComponent' with no type
  • Previous by thread: Re: FSAllocateFork
  • Next by thread: Re: FSAllocateFork
  • Index(es):
    • Date
    • Thread