by dgreenhbs99 » Wed Feb 01, 2017 8:30 pm
toolman, thank you for the expression of disbelief. Nevertheless, many files are corrupt; they are readable by Subsonic but not useable in any other way. They are now MIME-type binaries with gobbedlygook names like O2XRWX~U without a file suffix. They are listed as type binaries/octet-stream -- which to me, means that they are files that were midstream somewhere between server and client, under the care of Subsonic, if you will, when some freak event happened. I cannot generate MIME-type files; I assume Subsonic does. I also assume the fact that Subsonic can still read them is a bit of a black swan event.
As they are MIME-type, I cannot append "flac" or "mp3" or anything to get them to play; I can only play them via Subsonic. It is not entire directories; only certain tracks. For example, whatever corruption happened often affected only certain tracks, leaving others intact and readable. In a couple of instances, entire directories were corrupted, and although Subsonic could still play the music therein, I could not enter the folder from the terminal or gui, even in superuser mode, because the "directory" was not longer recognized as a directory by Ubuntu.
I am using, and have always used, default flac transcoding.
The files are mostly (although not entirely) those I have accessed from my Android client. A few are older files (8 months old-ish) that I never attempted to access from Android, but likely were accessed from other clients in our household.
I have had to restart Subsonic now and then, so the log file is not dispositive...frankly, the log doesn't go back far enough for me to see what might have happened.
To refine the question: When something fails, Subsonic appears to be abandoning the flac files as MIME-type binaries. If I could learn what is causing this, I could try to take steps to avoid these circumstances in the future.
Thank you for any insight anyone may have on this.