Disk write error for Steam Workshop updates

[Tiagoquix]

Your system information

• Steam client version (build number or date): Stable Client, 1715635533
• Distribution (e.g. Ubuntu): Fedora Linux 40 KDE
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes
• Steam Logs: steam-logs.tar.gz
• GPU: NVIDIA GeForce GTX 1050 Ti

Please describe your issue in as much detail as possible:

When I open the Steam Client and then click to play Team Fortress 2 (or any other game possibly, but I only saw this occur with TF2) and it has to download an update for a Workshop map that I'm not subscribed, but that I have played on it (because of servers hosting Workshop maps with tf_workshop_map_sync WORKSHOP_MAP_ID), the game gets stuck at "Downloading Workshop (0%)" until I manually go to the Steam Client "Downloads" section, see that the game has "Disk Write Error" and manually press the "try again" button to make the game launch properly.

The error then goes away and everything works as expected, but it always happens when something from the Steam Workshop has to be updated and then manual intervention is required.

My Steam Library files are at /mnt/HDD/SteamLibrary (then /steamapps/workshop).

To be clear, the files are saved correctly after the manual intervention.

Steps for reproducing this issue:

Explained above.

[jorp]

Hello, are you using BTRFS? Can you include an output of dmesg shortly after this happens?

[dsalt]

I've just looked at the log text here (as it's another instance of DISK WRITE ERROR lacking context; see #7958) and the relevant parts look suspiciously similar to #10906.

[Tiagoquix]

Yes; I'm using BTRFS. If the error happens again, I'll post an output of dmesg.

[jorp]

Yes; I'm using BTRFS. If the error happens again, I'll post an output of dmesg.

I would recommend testing your RAM as well

[Tiagoquix]

I ran a memory test with the latest version of https://memtest.org/ for an hour and didn't get any errors.

[Tiagoquix]

@jorp Hi there. The error happened again. Here's the sudo dmesg output shortly after it happened: https://0.jaegers.net/?3a38abb7d32ab972#DaaLLBggVjLsaQjjmxPfoiQ4kcLortNkoMFHzFAyfd99

[dsalt]

So no hardware problems and no storage failures; as expected, given what I've seen here. As mentioned in another bug report, Steam really needs to report and log at least strerror(errno) (or equivalent; ideally, also errno to avoid any need for translation).

[Tiagoquix]

FYI, the same problem happened again for me with Steam Workshop updates and also for normal updates (and then proceeding normally with or without manual intervention), but there's no errors/warnings about BTRFS in sudo dmesg.