[Bug 9258] New: free space is based on dosdevice free space, rather than partition free space

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

Summary: free space is based on dosdevice free space, rather than
                    partition free space
           Product: Wine
           Version: 0.9.34.
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

wine will return the incorrect amount of free space to applications under
certain common scenarios.  it appears that the free space is determined by the
dosdevice that has the directory that the application is running from.  it
should be expected that the free space returned would be based on the partition
that has the directory that the application is running from instead.

let me provide an example to clarify.  i've installed steam to
/home/user/games, which falls under the z:/ dosdevice, which is a symlink to /.
 / and /home are on different partions:

$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda3             9.2G  7.9G  914M  90% /
/dev/hda6              63G   30G   30G  50% /home

i am trying to install half-life2 via steam, which should be fine because i
have 30 GiB of free space in /home.  however, the steam application says this
is not possible because there is only 914 MiB of free space, and the game needs
3.8 GiB total to install.  wine is providing the free space for / instead of
/home to the application.

note that if i install the game to /home/user/.wine/drive_c/steam, then wine
correctly returns 30 GiB free space to steam and i can install the application.
 i believe this is because the drive_c directory appears to be under the c:/
dosdevice, rather than the z:/ dosdevice.  this is a solution, but it is far
from optimal to be forced into arranging my files in a way that i don't want
to.

so i think the problem is that wine returns the size of the partition of the
dosdevice that apparently has the working directory, rather than the size of
the partition that actually has the working directory.

i still don't think i've clearly explained this, so if you have questions,
please ask.

thanks for all the hard work on wine.

mike