I know Linux users historically like command line utils, but I like a GUI when it gives more options. File renaming is a case in point and although it took me a few tries to get to grips with Bulky, it can do about 70% of what I commonly use Bulk Rename for in Windows.
However, having become used to it being quick and easy I downloaded files direct to an SMB share (why download to my PC then upload to the server, do it direct!).
I then attempted to change the name on the files. I wanted to Capitalise various bits of the filename, so the Change Case Title Case option does this nicely.
However while it works fine on files on my local machine and it can do many of the other rename functions, iit completely barfs on the files on the SMB share. I get the error message
Unable to rename can't rename file, filename already exists.
The same behaviour can be seen if I access the files via a mount point in the file system that mounts the server share directly at boot.
Clearly this suggests something to do with the fact that it's an SMB share and case sensitivity on the rename but why?
All I can find through searching that's relevant are old posts about an SMB parameter (case sensitive = yes) that was an SMBv1 thing therefore shouldn't apply with v2 and 3
If it makes a difference it's a TrueNAS server, current version of appliance, having taken all the default options when setting up the share.
Anyone else encountered this and found a way round?
I know Linux users historically like command line utils, but I like a GUI when it gives more options. File renaming is a case in point and although it took me a few tries to get to grips with Bulky, it can do about 70% of what I commonly use Bulk Rename for in Windows.
However, having become used to it being quick and easy I downloaded files direct to an SMB share (why download to my PC then upload to the server, do it direct!).
I then attempted to change the name on the files. I wanted to Capitalise various bits of the filename, so the Change Case Title Case option does this nicely.
However while it works fine on files on my local machine and it can do many of the other rename functions, iit completely barfs on the files on the SMB share. I get the error message
Unable to rename can't rename file, filename already exists.
The same behaviour can be seen if I access the files via a mount point in the file system that mounts the server share directly at boot.
Clearly this suggests something to do with the fact that it's an SMB share and case sensitivity on the rename but why?
All I can find through searching that's relevant are old posts about an SMB parameter (case sensitive = yes) that was an SMBv1 thing therefore shouldn't apply with v2 and 3
If it makes a difference it's a TrueNAS server, current version of appliance, having taken all the default options when setting up the share.
Anyone else encountered this and found a way round?