Re: FSSetForkSize writing massive amounts of data over network?
Re: FSSetForkSize writing massive amounts of data over network?
- Subject: Re: FSSetForkSize writing massive amounts of data over network?
- From: James Bucanek <email@hidden>
- Date: Wed, 2 Feb 2011 22:40:27 -0700
George K Colley <mailto:email@hidden> wrote (Wednesday,
February 2, 2011 5:27 PM -0800):
On Feb 2, 2011, at 4:22 PM, Jim Luther wrote:
I was writing a similar answer. The only minor correction I'll add is:
FSSetForkSize() sees that you are making the file larger and so the File
Manager is writing a single byte of 0 at the new EOF - 1. If a file system
doesn't support sparse files and doesn't do an optimization (as Mark
explained below) like HFS Plus (and that kind of optimization wouldn't be
possible on a network file system), then the file system will have to write
zeros to fill the space between the old EOF and the new EOF to have correct
POSIX behavior.
If this is a network volume then depending on the server you could see long
delays if the file is big enough. For example for some SMB servers this will
cause the client to write out zero till it reaches the new eof.
Agreed, but I'm still shocked that this is happening on an HFS+
volume on OS X running Apple's File Sharing.
--
James Bucanek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden