Hmm… the best way to debug that I think is to do a full scan at debuglevel 9. Then search through the debug log to find each “component” of the path… like “/mnt/m3”, then “/mnt/mp3/new music”, then “/mnt/mp3/new music/from work”, etc and follow the scanning process of a song that doesn’t appear.
If it doesn’t scan it, it will emit *some* kind of error about it. Whether it’s an error about bad permissions, or metadata it doesn’t understand or whatever. Something will be logged.
Debug level 9 does not output any error messages, I am afraid.
Someone had a patch to push up the debugging info for failures to scan, and I might do something like that — throw up more visible errors for scan failures on first run only, so that the logs don’t get swamped with stuff, but problematic files are still visible on low debug levels.
I have not been able to track that patch down
Valdemar