http://bugs.winehq.org/show_bug.cgi?id=14914
--- Comment #2 from Marcus Blomenkamp mblomenk@gmx.de 2008-08-19 13:50:43 --- The attached trace has been generated by running win32 program (utorrent.exe) that creates a file of certain size and then writes to the file in non-sequential manner. The trace corresponds to that part where it creates the file. The writing part is done on a seperate file handle and it not relevant here so i did not include it in the logs.
The described behaviour happens with every program that runs a similar sequence of kernel32 calls so i do not quite understand what testcase you need.
I see the main problem in sematics: Should wine export Unix file allocation sematics or should it export native WIN32 NTFS file allocation? I do not know enough about Wine in order to define whats right and whats wrong but i would prefer NTFS file allocation semantics because it would give proper results for those programs that actually care.