Spotify was caught before (in 2016) doing exactly that -- https://arstechnica.com/information-technology/2016/11/for-f...

Only after publication on news sites they fixed it.

Won't be surprised if the bug regressed and happened again.

I don't use Spotify (not available in my country), so I wouldn't know, but I bet half of the reports are because of some badly written third party app constantly writing in 4kb chunks with O_DIRECT or fsync() all the time.

You'd have to verify I'm right, but this page describes how to change the cache location: https://support.spotify.com/us/article/storage-and-data-info...