06-20-2024, 02:40 PM
OK, I give up.
Fresh burn with @eaDir in the mpdignore and SMB library configured. = Successful scan.
Fresh burn with no mpdignore and SMB library configured = Freeze. - so far so good
Fresh burn with no mpdignore and NFS library configured = Successful scan.
Fresh burn with @eaDir in the mpdignore and NFS library configured = Freeze - What?
Fresh burn with @eaDir in the mpdignore and SMB library configured (again)= Freeze.
I must have run 20 combinations today and while NFS and ignoring the eaDirs seems to be more likely to complete, it isn't ever certain.
I did manage to get a moodeutl -m reading as a freeze happened and the cpu was heading north with the last reported value at 98%. Tried to run TOP for a few scans to see what process might be to blame, but it never managed to capture stats just before the freeze.
I really thought I had it this time.
Fresh burn with @eaDir in the mpdignore and SMB library configured. = Successful scan.
Fresh burn with no mpdignore and SMB library configured = Freeze. - so far so good
Fresh burn with no mpdignore and NFS library configured = Successful scan.
Fresh burn with @eaDir in the mpdignore and NFS library configured = Freeze - What?
Fresh burn with @eaDir in the mpdignore and SMB library configured (again)= Freeze.
I must have run 20 combinations today and while NFS and ignoring the eaDirs seems to be more likely to complete, it isn't ever certain.
I did manage to get a moodeutl -m reading as a freeze happened and the cpu was heading north with the last reported value at 98%. Tried to run TOP for a few scans to see what process might be to blame, but it never managed to capture stats just before the freeze.
I really thought I had it this time.
----------------
Robert
Robert