search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.23k stars 175 forks source link

SteamCMD - ability to disable pre-allocation (ZFS backed storage) #8745

Open BloodyIron opened 2 years ago

BloodyIron commented 2 years ago

I don't know the best place to put this as my cursory searching has not found a place, so I'm posting it here.

I'm working on running srcds/steamcmd servers in docker containers, and using SMB shares as the mount point for the data backed by my FreeNAS with ZFS as the underlying storage tech. ZFS itself does not support pre-allocation due to it being a COW tech.

Enabling "strict allocate = yes" at the Samba server/share scope (both/separate/wtvr) does not actually improve the situation.

To add some details, right now I'm trying to get steamcmd to download content for a Rust server and it flips its bits at the preallocation %8.7 or so. And everything I find points to this being a preallocation issue related to ZFS>SMB>Steamcmd

To explain a bit more clearly, I have a ZFS dataset shared out via SMB, and then mounted within the docker container (again, via SMB) as the location where steam content is being downloaded to.

So... I can't figure out a way to get steamcmd to disable preallocation. So can we please get a launch parameter (or equivalent) to get steamcmd to disable preallocation? For scenarios like this, and others, where preallocation doesn't work.

BloodyIron commented 2 years ago

@kisak-valve am I to take it, by your labelling, that this is an appropriate place to put this? :) I hope so! :D

slawo commented 5 months ago

Can we get an option to not pre-allocate space on a given library. I have the same issue with ZFS.