HFS+ does not support sparse files. Therefore, the OS
must do what you observed: allocate the space and fill the file up
with zeroes at file close or flush. Period.
Therefore, you have two choices:
1. Use a different type of file system, like UFS, for this
particular file and application.
2. Live with it.
3. Use a sparse disk image file (which can be created with Disk
Utility/hdiutil), which will effectively do what you're looking
for, although with some amount of overhead because of the "wheels
within wheels" aspect of disk image files.
Best regards,
John Francini
At 12:31 -0400 6/10/06, Marc Van Olmen wrote:
hi,
I need to create a big file (20GB), the contents is not important,
will fill that in later, just the file size...
When I try to do this with lseek and then write one byte. as soon I
close the file, it takes a few minutes because it looks like the OS is
filling up the rest with 0x00 bytes during close or flush. File system
is HFS+
Any trick on how to prevent this from happening?
regars,
marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list
(email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
--
John Francini, email@hidden
"The journey
is more important than the destination-that's part of life. If you
only live for getting to the end, you're almost always
disappointed." -Donald
Knuth
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
