This also happens to me with SMB share.
System info:
Client version: 1494374828
Distribution: Arch Linux
Opted into beta?: Yes
Checked for system updates?: Yes
More details
Steam sees available space fine when mounted through gvfs, it seems to be only misbehaving when the share folder is mounted manually using cifs
Same problem here with sshfs on Arch Linux. This used to work just fine.
Any news on this? It's holding back my recent purchases.
This is from the console output when trying to install a game:
../tier1/fileio.cpp (3268) : Assertion Failed: Failed to determine free disk space for /media/STEAM, error 75 Assert( Assertion Failed: Failed to determine free disk space for /media/STEAM, error 75 ):../tier1/fileio.cpp:3268
And, this is the crash ID:
CrashID=bp-f1a51323-f084-49b9-ac9a-5f8d72170702
Seems to work again on sshfs.
Still an issue here (Ubuntu, Fedora, openSUSE clients with Debian, CentOS NFS servers)
Problem still exists with NFS on Manjaro 17.0.2 and Debian 8.9 as NFS server.
This setup worked before.
Switching to SMB or SSHFS didn't work for me either.
But sshfs gave me another error: "New Steam library folder must be writeable" even though I have write permissions and it even could create a new SteamLibrary folder.
I am using steam beta version 1503954609. Non beta version also didn't work but I tested just NFS with that.
It works perfectly on kernel version 4.9 but on 4.13 it just shows 0MB space left.
I'm also experiencing this issue. Steam library on CIFS mount shows 0 bytes of free space. Would greatly appreciate this being fixed.
also have this
4.13.9-1-ARCH #1 SMP PREEMPT Sun Oct 22 09:07:32 CEST 2017 x86_64 GNU/Linux
Steam-native no beta.
Per #5364 Kernel 4.13 and 4.14 on ubuntu 16.04 have the same issue. I might have upgraded kernels around that time originally while trying to update amdgpu-pro drivers. beta makes no difference
Error still exists, running ubuntu 16.04, kernel 14.14.
Just tried to install a new game, unable to install Dead Maze, reports 0 space on NFS mounted home directory. Updates to Factorio succeed.
Also affected on Manjaro with a NFS share
Possible workaround
NFS Server: FreeBSD 11.1
NFS Client: KDE neon User Edition 5.12 (based on Ubuntu 16.04, kernel 4.13.0-38-generic)
When I switched from NFSv3 to NFSv4 it started working.
I have this issue too, with Ubuntu 18.04, Steam built Jun 1 2018 at 10:15;49, Kernel 4.16.10
Server is Ubuntu 17.10 with Kernel 4.13.0
This worked until a point, but I have no idea what that point was. Games just stopped installing.
Regarding switching to NFSv4, I thought that required Kerberos etc? Possibly a little heavyweight for general home users?
`@HughPH you dont need it, you can use the same style as v3. What you have to look for is "sec=sys" option, that will take you away from kerberos.
I dont have the server setup for linux since mine is on freebsd, but I can give you what I remember from my setup (server 1.2.3.4, client 4.3.2.1):
Client
/etc/fstab: 1.2.3.4:/PATH/TO/SHARE /PATH/TO/MOUNT nfs defaults,exec,nofail,vers=4 0 0
/etc/idmapd.conf: Domain = mydomain
Server (freebsd not the same as linux conf)
/etc/exports:
V4: / -network=4.3.2.1 -mask=255.255.255.255
/PATH/TO/SHARE -maproot=USER 4.3.2.1
/etc/rc.conf:
nfsv4_server_enable="YES"
nfsuserd_enable="YES"
nfsuserd_flags="-domain mydomain"
@penetal Thanks for the info. I managed to move it to v4 with a bit of googling, but unfortunately it hasn't made any difference for me.
Another symptom - I don't know if anyone else has it? Even with the default folder in ~/.steam and plenty of space on my local disk, I can't actually install anything - it declares that there's no space left even before it asks me where I want to install, and even if local (with space) is default.
A very untidy, hacky work-around is to exit Steam, unmount, reload Steam, install locally, exit Steam, remount, move the files, reload Steam, and - if necessary - re-add the remote Steam folder. Although that's not exactly practical if you want to install a 50Gb+ game and don't have 50Gb space on your local disk...
My fileserver and gaming machine are on a 1Gbps switch, so I thought about trying iSCSI. I'll let you know - although having this fixed would be a much better answer for most people.
-- EDIT --
iSCSI is really good, but it's weird to set up. I haven't done a great deal with it yet, but I don't think I've seen HalfLife 2 load so fast on NFS.
This tells you how to create a totally unsecured or slightly-secured iSCSI target, although I haven't got the daemon running properly on the server yet: https://fedoraproject.org/wiki/Scsi-target-utils_Quickstart_Guide
I created a 1TB file and used that as the block store. Remember it needs a block store, not just a folder. It's a block device connector, not a file share - so you will need to create a partition and format it from the client, and you can format it with any filesystem... Ideally you'll want to use an actual disk as the block store. Which is fine if you already have a disk with your shared stuff on it. Mine is a ZFS pool. (So the 1TB "disk image" file is on the ZFS pool which is on physical disks...)
For Debian/Ubuntu the package is called tgt
This tells you how to set up the Initiator (client) on Ubuntu: https://help.ubuntu.com/lts/serverguide/iscsi-initiator.html
It is really weird. You set it up, run sudo iscsiadm -m node --login and it adds a new /dev/sd_x_
same issue here
kernel 5.1
I fixed this by creating a ZFS share limited to 2TB (if the size is bigger it will show 0 space free)
I fixed this by creating a ZFS share limited to 2TB (if the size is bigger it will show 0 space free)
Combined with the people here reporting this on iSCSI I think this is a FS too big bug.
I suggest we file a new error for filesystems over 2TB
@kisak-valve can we use the testimonials here to change #4982 to confirmed and get some progress to a fix?
@nyanloutre Thanks. https://github.com/ValveSoftware/steam-for-linux/issues/4952#issuecomment-494362796 helped a lot. Limiting my nfs share to 2TB made Steam figure out that I really do have disk space. (NFS via FreeNAS which uses ZFS.)
Can you run stat -f [nfs mount] on your nfs client system, do the same on the server side for the backing partition, and report the results?
Hello, per "Fixes to free disk space checks to address issues with some NFS mounts" in the 2019-11-07 Steam client beta update, please opt into Steam's beta client if you haven't already and retest this issue.
(more precisions)
Latest steam beta (Nov 7) comes with several changes to the way the client obtains free disk space information, which may help with this - please retest.
If you are still experiencing this bug, please set DBG_STAT environment variable before running steam and provide the diagnostic output to statfs64 and statvfs64 calls from Steam client stdout.
Let's just all track this at https://github.com/ValveSoftware/steam-for-linux/issues/4982 which has been more active anyway.
Your system information
Please describe your issue in as much detail as possible:
I have a NAS with a NFS share where my steamlibrary is stored. I can play games from it just fine but can't install a new one. Steam reports that I have no space left, but there is almost 3TiB free (filemanagers can see this).
I can't tell if it was working before because just recently set up the NAS, copying my steam library folder to the share. I only have a SSD in my gaming PC so space is an issue for local install.
In settings, the library in the NFS share shows there's 0MB available.
(EDIT): Game updates works.
(EDIT2): Ubuntu 17.04 also affected.
Steps for reproducing this issue: