From the VMware Virtual Disks: Virtual Disk Format 1.1 doc, it states:
Stream-optimized compressed extents are meant to be easily streamed over a network link.
They are designed to minimize the memory footprint of the server streaming the virtual disk
and also allow for the use of a simple client application.
Are there any guarantees about the grain ordering in the stream-optimized VMDK? For example, I have a client that wants to take a single pass to write all data to a destination disk. If there's a guarantee that the grains are in ascending offset order, it's simple to write zeros as necessary. If not, then I need to either keep track of unwritten sectors or zero out the disk before writing to the destination.
What's the best way to write a simple client to accomplish this task?
Thanks!
Mike