05-04-2019, 02:34 AM
(This post was last modified: 05-04-2019, 02:56 AM by TheOldPresbyope.
Edit Reason: added postscript
)
@Onionhead
So we're back to the same kind of output I was questioning on 4/22.
Now we know you have a Synology NAS (which have been a challenge for some folks to configure). Are you using SMB or NFS as your file-sharing protocol?
It looks like you have the following directory branch on your NAS
The first three lines of the output you posted say MPD tried to open a file named ".mpdignore" at each level. It threw an input/output error each time, which in normal conditions means a disk error.
Then, in the subdirectory
we start seeing the entries I questioned before:
I've never seen this behavior before with my open-source NASes whether using SMB or NFS, and attempts to search the web on the key points gets me hits on your posts here but not on any posts to, say, an MPD-related forum. There was an issue posted to MPD a long time ago about MPD ignoring the .mpdignore file (talk about irony!) using NFS.
The output is suggestive but I'm hesitant to call this an MPD bug without knowing more about the Synology NAS code. Sadly it's proprietary.
1) can you try again with MPD 0.20.20?
2) I'm just gropping in the dark, but can you post the output from the following command?
You can cut it off after the "The Collection" subdirectory if there are more at the same level.
Note the use of the backslash to make this work from the command line.
Regards,
Kent
[Added]
PS - You said
If "The Collection" is an album where no songs synch, could you also post the ls -lR output for an album subdirectory where some songs sync and some don't?
So we're back to the same kind of output I was questioning on 4/22.
Now we know you have a Synology NAS (which have been a challenge for some folks to configure). Are you using SMB or NFS as your file-sharing protocol?
It looks like you have the following directory branch on your NAS
Code:
Curated/Donna Summer
Curated/Donna Summer/The Collection
Curated/Donna Summer/The Collection/infoThe first three lines of the output you posted say MPD tried to open a file named ".mpdignore" at each level. It threw an input/output error each time, which in normal conditions means a disk error.
Then, in the subdirectory
Code:
Curated/Donna Summer/The Collectionwe start seeing the entries I questioned before:
Code:
Curated/Donna Summer/The Collection/@eaDir/.mpdignore
^^^^^^
Is this directory entry real? It seems artificial.
Curated/Donna Summer/The Collection/@eaDir/60 - Take Me.flac/.mpdignore
^^^^^^^^^^^^^^^^^
I'm willing to bet this is a name of your FLAC file
and not the name of a directoryI've never seen this behavior before with my open-source NASes whether using SMB or NFS, and attempts to search the web on the key points gets me hits on your posts here but not on any posts to, say, an MPD-related forum. There was an issue posted to MPD a long time ago about MPD ignoring the .mpdignore file (talk about irony!) using NFS.
The output is suggestive but I'm hesitant to call this an MPD bug without knowing more about the Synology NAS code. Sadly it's proprietary.
1) can you try again with MPD 0.20.20?
2) I'm just gropping in the dark, but can you post the output from the following command?
Code:
ls -lR /mnt/NAS/Curated/Donna\ Summer/You can cut it off after the "The Collection" subdirectory if there are more at the same level.
Note the use of the backslash to make this work from the command line.
Regards,
Kent
[Added]
PS - You said
Quote:Looking through MPD log seems like within a particular album some songs synch while others don't. Many Albums no songs synch.
If "The Collection" is an album where no songs synch, could you also post the ls -lR output for an album subdirectory where some songs sync and some don't?
