-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Steam "needs at least 250MB" free space when plenty of space #4982
Comments
Hello @apiontek, as a test, can you remove both the distro and valve variants of the steam package, then move ~/.steam and if it is there, ~/.local/share/Steam somewhere out of the way. Then add either the distro-provided or valve-provided steam package, but not both and re-run steam. |
I had already done that. I originally had distro-provided steam package installed. I removed ~/.steam and ~/.local/share/Steam, then did a find ~/ -iname "steam" and removed ~/.steampid, ~/.steampath, and ~/Steam I think. I then purged the distro-provided steam, downloaded steam-latest.deb, and installed that. Upon getting the same error, I submitted this issue. Just now however, I tried again, running This time I reinstalled the distro-provided package and had the same result. Tried again and reinstalled the valve-provided package, and have the same result. I get the error with both. |
Thanks for the confirmation @apiontek. |
As an update, since my root system is on ext4, I created a temporary /opt/steam folder with subfolders for .steam, local-share-Steam, and Steam, and did ln -s for each of them into the appropriate places in my homedir. Then, the steam installer worked fine. But when I remove the symlinks and move the folders into position, although Steam starts up fine, I can't install games because it reports 0 space free. So it seems I could run games with folders symlinked to an ext4 partition, but this isn't optimal for me. My root partition is a small SSD. I wonder if I can create a ZFS block device formatted ext4, and symlink again? I'll try that. Editing to add: creating an ext4-formatted zvol and symlinking the steam folders to folders on that volume, does work and allow me to install & run games. Not ideal, but I can run games for now! |
Same problem on Arch Linux when trying to add new Steam Library folder located on ZFS volume: Steam shows 0 bytes free space in such folders. |
Got same problem on gentoo |
Same problem on Xubuntu 17.04 |
Chiming in, Gentoo user here.
My specific console error:
|
Gentoo user x2, Steam Beta, same problem as with @cybik |
@kisak-valve when will this be fixed (or at least an option that allows you to skip checking free space)? It's a bit(very) annoying that i cannot use steam. |
Same problem with steam and gog installers under wine, maybe we need to report a bug to zfs. |
I'm starting to think we should bring in the zfs driver developers. |
I'm having the same issue with Steam on Arch. I'm using btrfs instead of zfs though, but trying to install Steam games to another drive mounted at /storage. Steam claims there are 0 bytes of disk space free, which isn't true. I've confirmed that reading and writing to the drive works. |
Seems valve fixed this in beta update. UPD: Seems something updated in system, because the Steam and GOG installers in Wine are now correctly show the free space. |
Thanks for testing @soredake, is anyone else having this issue with zfs or btrfs with the steam beta client? If needed, you should be able to manually opt-in to the steam beta with |
Steam package versions 1503954609, still can't install (reporting 0MB free). Using zfs, Steam Linux Native. |
Still happening on steam beta with package version 1503954609 on Manjaro 17.0.2 and ZFS v0.6.5.9-2 |
My free space is correct now and I am able to install games to libraries in my zfs datasets. This is on Fedora 26.
|
@nathandorsey gave me the idea of updating my zfs (0.6.x to 0.7.1), but I still have 0mb available.
|
@cybik i'm on 0.7.1 zfs, 4.12.8 kernel and 6.4.0 gcc, maybe this will help you. |
@soredake I'll update my kernel for funsies. |
Kernel updated, still an issue.
|
@soredake can you run this:
|
ryao have you tried the beta client yet? the most recent update for it on my system broke writing to the disk on nfs. not sure if this is related to either of those 2 bugs mentioned. it creates folders and then when trying to download updates/games it errors that it cant write to the download folder. |
I have the same problem, also running ZFS with 4TB of free space. Could this be related to a glibc update? |
Same problem. Linux Mint 19 AKA Ubuntu 18.04 with ZFS dataset mounted at I have 4.5 TB of free space. And proper rights. I just copied and removed a movie in my username to the ZFS dataset. This setup works on my other machine. Frustrating. Did something change since a steam update? @kisak-valve over the years I've seen this issue in one form or the other more often than I care for. Please please please add the option to ignore free disk space checks. Tuck it away as far as you like, but let there be a way. |
Redsandro have you tried the beta client? im getting worse results with that. It complains it cant write files. |
It is still outstanding as of latest Steam Beta and 4.19.0 kernel. ZFS changes are approved for 0.7.12. There's still implementation time after though. Valve could make this go away if they capped the freespace at something sane. This drove me a bit insane to the point I have a zfs filesystem for each title with a quota on their parent steamapps directory. On the plus side it allows for easy snaphots and moving data around to other hosts/vms (yay zfs send), but is a completely external process. |
The ZFS recordsize is possibly a red-herring as my home directory is mounted via NFSv4 and I'm now having the same issue after upgrading from Ubuntu MATE 16.04 to 18.04. I do have 4.2TB free in my home filesystem. Edit: I did as ryao suggested and created a separate filesystem with a 2T quota at ~/.local/share/Steam, then linked ~/.steam to it, and that seems to work so far. I only launched Steam and made sure it installed cleanly and got to the login prompt. |
In case someone else finds this issue like I did: I'm running steamcmd inside a docker container on a host with zfs and I worked around this error by adding |
Can you run |
On my desktop, my home directory (which will cause the failure, had to move it from here):
Same directory on the (ZFS) NFS server:
Again on the desktop, the directory in which Steam is now installed (and working, see below):
On the server (this is a ZFS filesystem in the same zpool, but with 2TB quota/size restriction workaround applied):
|
@glabifrons thanks - if you are up for a little more testing, would you mind reaching out to me directly? |
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 |
Multiple games will tell me that they are out "Out of Space" (most recently, "Oxygen Not Included" will eventually fail (after six hours of play or so) to save any more games, complaining that "At least 15MB of space must be available." Meanwhile, I am on XFS, and have at least 70G available (and millions of inodes.) Restarting the game "resolves" the issue, but why is this even a thing?
|
@AlbinoGeek would you mind running I'm mostly interested in the provided 'scout' binaries (e.g. steam-runtime) - source code is included too. Basically we think statvfs64 is broken for 32 bit binaries on a variety of partitions (XFS/NFS) - I'm not sure if it's a libc or kernel problem. We'll implement a fix in the Steam client but it's unlikely we'll be able to fix individual games. |
No difference. Does Steam run anything under a chroot or similar system? Is there any library redirection in play, or anything else that would result in a game executing out of a virtual filesystem? (This is a wild guess, but seeing snap and friends do this...) |
@AlbinoGeek thanks. From the Steam client perspective you should be set and it will understand that you have 70GB free on your root XFS partition just fine. We can't fix the game titles though, you will need to report to each developer individually that they should either provide a 64 bit version of their title or switch their 32 bit implementation to use the |
Next client beta (> Nov 28) will have an additional workaround for this situation: torvalds/linux@cc3a7bf#comments Hopefully this will address the remaining problems. |
Closing as fixed in the 2019-12-16 Steam client update. If anyone is still seeing this issue, it will need a new investigation. |
not too sure how you think this is fixed 80Tb free and steam thinks it can not install anything |
Your comment is confusing. |
not too sure how you think this is fixed 80Tb free and steam thinks it can not install anything
why wouldn't I have 80TB ? and I do not have my steam library in my /home either .... but that is what is seems to only use for free space checking |
You're complaining that it's checking your home - that's because that's where it stores the library. No-one can guess your configuration. If you want help, you're going to have to provide more info as to what custom configuration you've come up with. |
Your system information
Please describe your issue in as much detail as possible:
Running Steam for the first time on fresh install, system fully updated. My homedirs are ZFS datasets. This has worked in the past, on an Ubuntu 16.04 system, same ZFS homedir setup, but that may have been over 6-10 months ago, last time I used it.
In current environment, running steam I get error window "Steam - Fatal Error" "Fatal Error: Steam needs at least 250MB of free disk space to update." Running from terminal produces output (gist)
df -h output (gist) -- every partition available has plenty of space.
apt-cache policy steam output (gist)
i also see in the terminal output, "Steam needs to be online to update" -- I have an active network connection. It is non-standard, being a bridge on top of a bonded interface, but this also worked in the past.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: