[Bug 44679] New: Various apps: zero available disk space reported with Wine prefix on ZFS filesystem.

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=44679

            Bug ID: 44679
           Summary: Various apps: zero available disk space reported with
                    Wine prefix on ZFS filesystem.
           Product: Wine
           Version: 3.3
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: wine-bugs at winehq.org
          Reporter: wermaan at gmail.com
      Distribution: ---

I have installed Wine prefix on zfs pool:
Filesystem                  Size  Used Avail Use% Mounted on
datastorage                 3.6T  683G  2.9T  19% /mnt/data

Applications while running in Wine report zero available space. For example
built-in 'explorer' shows zero used space and zero available space for disc
'C'. This prevents any application which checks for disk space from installing,
e.g. I cannot install any game with gog launcher. Any application which doesn't
check space runs fine.

If prefix is installed on other partition everything runs fine.

The only difference in logs between normal and erroneous run is:

005d:fixme:ntdll:FILE_GetNtStatus Converting errno 75 to STATUS_UNSUCCESSFUL

I'm running Arch Linux with kernel 4.15.5-1.
Zfs kernel module: linux415-zfs 0.7.5-6, Zfs pool mount options: rw,xattr,noacl
I have tried Wine versions 3.2-1, Wine staging 3.3.r3576.1fdaf4c4 and 3.3.

I have debugged Wine and managed to pinpoint the source of the issue:

'file.c':3222, function 'NtQueryVolumeInformationFile'

    struct statfs stfs;
    if (fstatfs( fd, &stfs ) < 0)
    {
        io->u.Status = FILE_GetNtStatus();
        break;
    }
    bsize = stfs.f_bsize;

After this call to fstatfs 'errno' is set to 75 'Value too large for defined
data type' which probably means that there is an issue with 64 bit inodes. I
wasn't able to solve the issue by changing the call to fstatfs64 with statfs64
so maybe I probably got something wrong.

-- 
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.