here there be monsters: error indexing large databases

Help and Support Help
1

ok, I know this is a topic with an extensive past, but I may have some new information. I have read the FAQs, and the relevant topic is “Music on NAS not showing up in library”. I note that this particular FAQ ends with a 2014 posting and no clear resolution.
I have 2 volumio systems on raspberry pi(s). both mount music from a CIFS server (also a raspberry pi running raspbian, up to date). I have a very large (> 50,000 tracks) music repository on the CIFS server. The tracks are a mix of flac and mp3, and the metadata is accurate. There are 4 mounted filesystems (identical mounts on both volumio’s) which comprise the music repository. Originally both volumios were running volumio 2.323. I had been using both with the large mounted filesystems for months without issue. I upgraded one volumio and upon restart, browse/musiclibrary was empty. This is exactly the situation described in the FAQ mentioned above. Unfortunately, I didn’t note what the upgrade version was, but today I upgraded that volumio again, to version 2.361. The upgraded system also does not successfully initiate indexing and I still cannot see my mounted music libraries. Looking at volumio.log, I see 2 mpd errors:
error: MPD error: Error: connect EAGAIN /run/mpd/socket
info: Database scan error: Error: Command failed: /usr/bin/mpc update.

df shows all the CIFS shares are correctly mounted on the volumio system.

I deleted all the mounts and remounted only one of my music shares. its still indexing, but appears to be working fine with this smaller number of tracks.

so, this is ultimately an mpd problem, but volumio 2.323 appears able to handle my large shares, and volumio 2.361 (as well as some intermediate version I forgot to document) cannot. I suspect I’m on the edge of some mpd limit, but it appears the volumio upgrade put it over the edge. From the volumio FAQ, its unclear whether the original issue was ever resolved, but I’m well over the 10,000 track limit mentioned there and things worked fine with 2.323. Suggestions are appreciated, and an update to the FAQ would be great. volumio is a great system.

2

here is a bit more information on this problem. after mounting only one (very large) CIFS share, indexing proceeded normally and system use was nominal. I then tried adding a second share. I again got errors indexing, and browse/library is empty - even the first, successfully indexed share had disappeared simply because of the second mount. I deleted the second mount and restarted volumio, and the first share, previously indexed, reappeared and works normally. I have both of these shares mounted on my older volumio version, and they work properly there.

3

This is mostly a “me too” comment.

  • Have the exact same pb with my sftp mount.
  • Library has same numbers, and tags created with beets.