Cant add btrfs storage in steam
Im trying to mount my second drive (btrfs) and that works just fine for the system with "noatime,lazytime,commit=120,discard=async,compress-force=zstd:3,space_cache=v2,nofail" extra options from the docs page.
However it does not work to add this drive in steam, Searching I found several people saying steam needs to be mounted with execution permissions for it to work. So I tried to add ",exec" or ",exec,rw" to the end of bazzite suggested options but none has fixed the issue.
Starting steam from the terminal I can see there is a permission issue, I did run the following permission command "sudo chown $USER:$USER /var/mnt/storage" from the docs page.
sh: line 1: /mnt/storage/SteamLibrary/.steam_exec_test.sh: Permission denied
Failed system("/mnt/storage/SteamLibrary/.steam_exec_test.sh") in execute test: 32256
7 Replies
mount permissions look like this
I reformatted the drive and tried with a blank one but same result.
I tried these options instead "rw,noatime,users,exec 0 0", I was running these with nobara before switching to bazzite and it worked. Can now mount the drive but os seams to think that I'm using an SD card as storage judging by the icon?
So one of the options in the suggested line is not working with my setup. Understand I'm loosing out on the compression, keep the working options or what can I change to make it work?
compression should work if you just add its options
compress-force=zstd:3
test with sudo mount -a and it will tell you if anything is wrongThanks for the reply, I should have phrased my question better.
I can run the whole first line with suggested options without running in to an error with my operating system, it is just steam that doesn't work with it.
Guess I will have to try and add one option at a time and see when it stops working, was just hoping someone had run into this before so I didn't have to try em all.
it would be great since i cannot replicate it myself but we had a handful of users get the issue, so if you find the option that causes the issue, report it here and i will update the documentation
So I saw the new 3.0 was released and uppgraded to that, changed the options back to suggested ones and this time it worked just fine. Either it was the upgrade, or some strange bug that when I had managed to add the storage once it was possible to use suggested options after that.
This is what happens to others, a reboot magically fixed it and we are none the wiser