You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long File Names are truncated to their 8.3 versions for files and directories that are copied even when the LFN support driver is loaded. Which is unexpected since both DIR and COPY support them.
The text was updated successfully, but these errors were encountered:
I plan to add the lfn aware get/set attributes calls so long filename will be preserved. However, I am still trying to determine best choice of action for short filenames when doing so.
1 do nothing special, the short filename may be different depending on order copied (this will be the initial implementation)
2 after the copy, if verify is on, check and attempt renaming to restore short names (probably rename to some temp name, rename conflicting file if one, rename to desired name)
3 ensure order copied corresponds to sfn ~ sequence so correct sfn created.
4 something better
when copying via lfn api, lfn is primary name so if conflict in sfn, sfn truncated and ~# appended where # is incremented until no clash is found, thus if 2 or more files are copied with same sfn the order determines # given. this algorithm may vary by lfn provider and what files already exist at destination (ie may be treated as overwrite by filesystem instead)
Long File Names are truncated to their 8.3 versions for files and directories that are copied even when the LFN support driver is loaded. Which is unexpected since both DIR and COPY support them.
The text was updated successfully, but these errors were encountered: