Steam sometimes misleads: “DISK WRITE ERROR” #7958
Labels
Comments
I'm running into the same issue on Ubuntu 20.04. I've verified the file system is clean (ext4), the LVM is in good shape, and there are no SMART errors on the underlying disks. I'm seeing these in my steam logs:
|
|
I'm running into the same issue. It only affects the beta version of steam - the official version works fine. Using a secondary library (mdadm, xfs filesystem) I get disk write errors. If I "retry" the download the game will eventually install. Again, only affects the beta version of steam. |
|
@dsalt Steam may be allowed upto 2048 (hard limit) but what is the default. How are you determining it's steam specifically leaking descriptors and not a user limit? Kisak would know more if Steam is resetting ulimit somewhere but I recall needing to force a default for something unrelated to this. Same core issue though. lsof output should give some idea where they are being consumed. |
|
@h1z1, wrong report. (That said, I'll need to run |
|
#10906 is another instance of only the fact that an error has occurred being recorded: neither the error number nor description are present. |
This was referenced May 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've just been having a problem when trying to download updates for Proton Experimental (see #7956). The thing which I'm reporting here is that “DISK WRITE ERROR” isn't necessarily an actual disk write error, but I have to assume that it may be; consequently, my first action on seeing this is to check the kernel log.
Steam needs to be better at reporting these things to the user.
In my specific case, there's a lot of text in
…Steam/logs/content_log.txtlooking likeThis is EMFILE, “Too many open files”. (Steam is allowed 2048 open files; the usual limit is 1024. It could be that there's a resource leak somewhere.)
I suggest fixing this by doing something like mapping possible errno values to severities and, on seeing an error which is more severe than any already received for the current operation, storing that one for display. Or perhaps just reporting the first one…
As for error display,, I'd show the text associated with the recorded errno value, i.e. the output of strerror(). Or at least some text which isn't “DISK WRITE ERROR” when the error is something else.
The text was updated successfully, but these errors were encountered: