tmp partition filling up using snapcast + spotify

Hey all, I’m new here… just set up a rPi3+HiFiBerryAmp2 for my Livingroom & PiZw+sx400 Amp Hat for the bedroom. Both are running Volumio 2.310 (which is fabulous!). I’m using Saiyato’s snapcast plugin (fabulous) along with volspotconnect2 (fabulous) to stream Spotify to both rooms in sync… and it works very well. HOWEVER…

I’m having an issue where after about two or three hours of music the Spotify stream just keeps dropping off, and I can restart it and reconnect to the volumio instance but it drops again almost immediately after it starts playing.

I have noticed that a reboot fixes the issue. I have also noticed with df -h that the /tmp dir is empty at boot time, but slowly fills up while streaming music and when it gets to 99% full the stream starts dropping out. A reboot fixes it every time. But doing that is already getting old.

I have a 32GB card and the /tmp partition is only 480mb and fills in a few hours.

I’m wondering if anyone else has seen this issue? and what is the best way to fix it? I was thinking about maybe expanding the /tmp partition, but that kind of seems like it would still have the issue, it would just take longer to fill /tmp and see the issue each time. How can I stop it from filling up and killing my Spotify stream?

All ideas welcome, thanks for looking!

root ls:
2017-11-09 at 20.10.png

/tmp ls:
2017-11-09 at 20.20.png

Great research and good work on the print screens. I must admit I don’t know where the files are coming from. I do know that Spotify tends to cache a lot and it can grown up to a gig on my PC.

I’m not at home and won’t be for a few days (work), is there a way for you to check if it’s really Spotify or maybe Snapcast? That way we can create issues for the matter. :slight_smile: I do presume it’s the Spotify cache, but it’s nice to be sure.

You say you are using volspotconnnect2, this uses libreelec and the latest versions allow you to disable the cache. You can do so by editing the startconnect file in /data/plugins/music_service/volspotconnnect2

Let me know if this helps.

Cheers

The cache is already disabled in volspotconnect2

Thanks for the replies fellas - Balbuze: it looks like on my system it is using a cache according to the file Saiyato pointed out…

2017-11-10 at 09.27.png

This not the file from my plugin, but the patched from Sayiato. Maybe he could change his patch… :wink: And disable-audio-cache

I’m curious… whats the point of the cache? is it a “buffer” so music doesn’t stutter during network slowdowns? or is it a classic cache in the sense that the music files are saved in case you play them again, they don’t have to be re-downloaded?

It would be awesome if Saiyato would add an option to the plugin UI to either disable the cache completely (if it is indeed not needed) or place it in a directory of your liking… for instance, if /tmp is too small (which it seems to be in the case of volumio).

@balbuze… I just reloaded two of my devices… starting from scratch to iron out some kinks and I have only loaded your plugin (volspotconnect2) so far and I still see the -c /tmp in there (same on both devices) … so I don’t think it is Sayiato’s plugin making that setting… :question:

2017-11-10 at 13.53.png

2017-11-10 at 14.00.png

the /tmp is used only to store credentials…

I don’t know what files are stored in /tmp, but the /tmp/snapfifo file is needed for snapcast.

The other files might be Spotify files, I will patch the plugin to add the disable cache parameter to the amended template for volspotconnnect2.

Update: I’m still experiencing this issue, it is only once the snapcast plugin gets installed. I have tried the latest version to no avail. So I opened an issue with your repo https://github.com/Saiyato/volumio-snapcast-plugin/issues/30 to track. Hopefully, you can help. thanks!

Update for anyone that may be having a similar issue: The plugin was updated and fixed by @saiyato. See here: github.com/Saiyato/volumio-snap … /issues/30