[Bug 14914] files are created as sparse files when they shouldn't

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Aug 21 03:35:18 CDT 2008


http://bugs.winehq.org/show_bug.cgi?id=14914


Marcus Blomenkamp <mblomenk at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |UNCONFIRMED
         Resolution|INVALID                     |




--- Comment #11 from Marcus Blomenkamp <mblomenk at gmx.de>  2008-08-21 03:35:17 ---
Didn't i expect that? ;)

NTFS supports sparsefiles, under Windows as well as under Linux/NTFS-3G. But
under Windows sparsefiles are not actually created, UNTIL the application
EXPLICITLY asks for it (by means of an ioctl). But under Wine the opposite
happens: files are sparsefiles used until the application manually writes to
the file completely.

The problem that i have described is a real one. It is neither a problem of the
application, nor a problem of the filesystem (btw: do you know any usable
filesytem under Linux, that does not support sparsefiles?), it is a problem
with wine: Primarly it is the question whether Wine wants to export Windows VFS
API semantics or whether it wants to export Unix filesystem semantics. If Wine
wants the former, then this semantic difference should either fixed or be made
configurable so that the user can decide which suits his needs best. Samba for
example has a tuning knob for this.

As my 'testcases' are not sufficient obviously, then please describe exactly,
what i should supply.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list