FileBot

Hello,

I know I can find missing episode with the command "filebot -script fn:miss -log off /path".

Recently, however, I own the DX513 expansion unit and have therefore split some series. Therefore, I once asked if it is possible to search for several paths at the same time.

So something like "filebot -script fn:miss -log off /volume3/......./ volume6/........".
Or another possibility?

Best regards

Checked the code. Should work. Have you tried yet?

Yes I have but it is only the "first path" searched. /volume6/ is apparently ignored

So /volume6/ works if you pass it as first argument?

Note that miss only works if files are xattr tagged. You can use the xattr script to view xattr, to confirm that files on volume6 have xattr.

It doesn't specifically take argument 0 but just takes all files from all arguments, so I'm fairly sure that it works:
https://github.com/filebot/scripts/blob ... .groovy#L9

That seems to be the reason.
I just tried it with /volume/, which did not work.

But I do not understand why?
When the files were on /volume3/ the xattr´s were still there and although I moved the files from /volume3/ via the DSM Filestation to /volume6/, the xattr´s now seem to be "buggy".

Here's an example: WTF.
Now I have to look with how I can repair the xattr without the files being renamed.

1.
xattr can be binary data, so the xattr you see here are not buggy, just aren't plain text data. Looks like Synology DSM uses those for some purpose.

2.
This may indeed be a bug with Synology DSM, not preserving Linux filesystem metadata when copying files between file systems / drives. You could run a few tests with mv / cp / rsync and see what happens to xattr if you move files from one drive to another yourself. If DSM uses rsync internally, or it's own copy code, then not copying Linux xattr might be considered a bug, or a feature, most likely an oversight since xattr isn't widely used.

Script Repository ➔ Find missing Episodes