search

ValveSoftware / steam-for-linux

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

Automount and second steam library folder #9695

Open Quentin-ctrL opened 1 year ago

Quentin-ctrL commented 1 year ago

Your system information

Please describe your issue in as much detail as possible:

Second Steam library (path : /data/Games) is not detected properly. It's located on a second hard drive. See fstab for /data/Games UUID=2631a47a-0c80-47fa-a5ff-7f121f033d5d /data/Games/ ext4 defaults,nofail,noauto,x-systemd.automount,x-systemd.idle-timeout=600 0 2 No issue to mount and a simple ls /data/Games/ before starting steam client to see the library Otherwise, the library is not detected and I had to add it manually.

Steps for reproducing this issue:

  1. Add a new steam library folder on a second hard drive /data/Games
  2. Set automount on /data/Games
  3. Start steam client

check if /data/Games is mounted viadf -h before and after

10leej commented 1 year ago

Your system information

Please describe your issue in as much detail as possible:

I use a NFS export to manage my steam library due to rural internet, since the latest client update came in I can no longer moun t eh share. I have checked user permissions on the file server and they do work. Open steam > Settings > Storage I no longer see the folder selected and the steam client is not spawning the file picker dialogue.

Steps for reproducing this issue:

  1. Attempt to use a nonstandard library path.
10leej commented 1 year ago

Check with the flatpak seems the issue is there as well.

mAd-DaWg commented 1 year ago

I have a similar issue but perhaps it may be unrelated.

I have a ntfs drive mounted on /home/who/Storage using the the following fstab options as per the steam guides: /dev/disk/by-uuid/ /home/who/Storage ntfs-3g defaults,locale=en_US.utf8 0 0

The hard drive works correctly and has zero issues with all other applications aside from steam. I have run filesystem checks and S.M.A.R.T reports on the drive and 0 issues where found.

When steam launches and tries to access the steam library on the ntfs drive, It has some sort of error(see attached log) that seems to be something to do with the shadercache. It then puts the drive into a weird errored stated which causes the mount to be inaccessible to both steam and ubuntu.

It seems to be an issue with steams error handling where it does not properly handle file opperation errors, and then doesnt handle the error correctly breaking the mount. Clearing the shader cache alleviates the problem for 1 steam luanch, however the very next steam launch again breaks the mount again.

To note: the folder ~/Storage/SteamLibrary/steamapps/shadercache/2420510/nvidiav1/GLCache takes quite a while to delete which is related to the "HoloCure - Save the Fans!" game

Reproduction

  1. Mount ntfs drive with steam library on it with following fstab entry: /dev/disk/by-uuid/ /home/who/Storage ntfs-3g defaults,locale=en_US.utf8 0 0
  2. Launch Steam
  3. Steam cloud sync reports failure and game updates report disk write errors
  4. Close steam
  5. Remount ntfs drive
  6. Clear cache folders in ~/Storage/SteamLibrary/steamapps/
  7. Launch steam again and client temporarily works
  8. Restart steam
  9. Issue re-occurs

Screenshot from 2023-09-25 20-03-42 Screenshot from 2023-09-26 14-24-23 steamlog.txt assert_20230926134312_34.zip

System Information

10leej commented 1 year ago

I took some in estimating this, turns out I was missing xdg-desktop-portal-gtk as xdg-desktop-portal-wlr does not have file picker support.

Joshua AE Lee  https://10leej.com/stalker

Sep 26, 2023, 8:42 AM by @.***:

I have a similar issue but perhaps it may be unrelated.

I have a ntfs drive mounted on /home/who/Storage using the the following fstab options as per the steam guides: /dev/disk/by-uuid/ /home/who/Storage ntfs-3g defaults,locale=en_US.utf8 0 0

The hard drive works correctly and has zero issues with all other applications aside from steam. I have run filesystem checks and S.M.A.R.T reports on the drive and 0 issues where found.

When steam launches and tries to access the steam library on the ntfs drive, It has some sort of error(see attached log) that seems to be something to do with the shadercache. It then puts the drive into a weird errored stated which causes the mount to be inaccessible to both steam and ubuntu.

It seems to be an issue with steams error handling where it does not properly handle file opperation errors, and then doesnt handle the error correctly breaking the mount. Clearing the shader cache alleviates the problem for 1 steam luanch, however the very next steam launch again breaks the mount again.

To note: the folder ~/Storage/SteamLibrary/steamapps/shadercache/2420510/nvidiav1/GLCache takes quite a while to delete which is related to the "HoloCure - Save the Fans!" game

Reproduction Mount ntfs drive with steam library on it with following fstab entry: /dev/disk/by-uuid/ /home/who/Storage ntfs-3g defaults,locale=en_US.utf8 0 0 Launch Steam Steam cloud sync reports failure and game updates report disk write errors Close steam Remount ntfs drive Clear cache folders in ~/Storage/SteamLibrary/steamapps/ Launch steam again and client temporarily works Restart steam Issue re-occurs

https://user-images.githubusercontent.com/5232999/270657943-11e57db9-ad00-4010-9682-ce9f7aaa5e35.png

https://user-images.githubusercontent.com/5232999/270657980-6f3a8cb1-87e1-4ca3-bebd-c77aee3be4c9.png

steamlog.txt https://github.com/ValveSoftware/steam-for-linux/files/12727569/steamlog.txt assert_20230926134312_34.zip https://github.com/ValveSoftware/steam-for-linux/files/12727577/assert_20230926134312_34.zip

— Reply to this email directly, > view it on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/9695#issuecomment-1735467753> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AARHLHMZPYTGN52WGPL5YTTX4LERVANCNFSM6AAAAAAZQB24HE> . You are receiving this because you commented.> Message ID: > <ValveSoftware/steam-for-linux/issues/9695/1735467753> @> github> .> com>

Matthew0x commented 9 months ago

Sorry for "hijacking" the issue slightly, but it's related to NTFS and Steam. I think it might have to do with mount/autofs, but I don't think they even host on GitHub.

I have originally been using an NTFS drive with games exclusively for Steam and it is possible to make it work with both FlatPak and native Linux version of Steam - that works (I had it mounted similarly as OP).

The problem is, I have had a very persisting issue that would go away and come back (but mostly remain) and I seemingly narrowed it down to a literal spam of errors in the logs under "mount.ntfs". I don't know whether it has something to do with files that Steam might produce in there (the issue was gone after I removed the games drive), or maybe it's the filesystem itself, but I took my only NTFS drives, formatted them and ... the issue is seemingly gone (I think closing System would help me sometimes).

Symptoms:

Samples of errors (these 3 errors repeat infinitely and get generated all the time in the logs): Failed to add FILE_NAME attribute. Failed to add resident attribute: Numerical result out of range ntfs_non_resident_attr_expand_i: bounds check failed: Numerical result out of range

PS: I am also not sure if this has to do with Steam specifically, but I experienced poor performance of Steam client, including crashing, process restart etc. After I removed the NTFS drive it works much better (it could be a coincidence however).