Moving to nfs broke

[Razze]

Hey there,

the last (or one of the last versions) seems to have broken moving to nfs drives

A invalid characters dialogue comes up on rename

https://imgur.com/a/00ZSO4F

This usually only happens, if the nfs drive was not mounted on trying to rename. You can access the drive and thus mount it and then hit rename in filebot for it to be okay.

[rednoah]

This usually only happens, if the nfs drive was not mounted on trying to rename. You can access the drive and thus mount it and then hit rename in filebot for it to be okay.

File path validation will indeed flag : colon and friends. File paths that are known to exist will not be flagged. So FileBot will complain about creating new folders (i.e. file paths that do not currently exist) that contain : colon and friends, so that might explain why you might be seeing this type of warning when a target file system is not yet mounted.


How did you load a file path into FileBot that doesn't exist at the time from the point-of-view of your machine? Opening a network folder to drag-n-drop files into FileBot will typically ensure that said network folder is mounted and thus exists.


You can click Continue to continue as-is with the proposed file path:
(NOTE: if this will auto-mount the desired network folder, or just create a new folder in your local file system is another question; IDK how GVFS would work exactly in this case)



You can also permanently disable file path validation via the advanced settings. Please read [DOCS] Target Unix Filesystem for details.

[Razze]

I'm moving stuff from a local filesystem to a nfs.
I'm setting that folder in my template for that type of media.
And that has been working for years at this point.

I was not aware, that you could actually proceed without applying
But in that specific case, it won't help since the filename also has a colon, that should be cleaned up

[rednoah]

But in that specific case, it won't help since the filename also has a colon, that should be cleaned up

Well, that you can fix in your custom format. Just replace all the : colon at format time, e.g. the {plex} format guarantees file paths without : colon, but you can do replacement with custom code as well.

I'm setting that folder in my template for that type of media.

Might work. I strongly recommend mounting the target file system first though. I could guess that indicators / warnings for overwriting existing files and the like will not work if at format time some target path does not exist according to the OS, but then later on once we move files - and GVFS auto-mounts the file system - suddenly does exist. The code definitely does not account for that kind of thing. It's probably fine, but I could also imagine some strange behaviours.

[Razze]

I'm setting that folder in my template for that type of media.

Might work. I strongly recommend mounting the target file system first though. I could guess that indicators / warnings for overwriting existing files and the like will not work if at format time some target path does not exist according to the OS, but then later on once we move files - and GVFS auto-mounts the file system - suddenly does exist. The code definitely does not account for that kind of thing. It's probably fine, but I could also imagine some strange behaviours.

That's what usually worked before. I was able to just access the nfs drive before moving and then it worked fine.

[rednoah]

That's what usually worked before. I was able to just access the nfs drive before moving and then it worked fine.

Yep, I would imagine that some actions, like opening the folder via the file browser, perhaps even file read / write operations, etc will auto-mount the network drive. While other other file system operations like file listing, stat calls to check if a file path exists, etc, do not trigger an auto-mount. I'm no expert on how GVFS works exactly though.