Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No LFN Support #11

Open
shidel opened this issue Aug 16, 2024 · 1 comment
Open

No LFN Support #11

shidel opened this issue Aug 16, 2024 · 1 comment

Comments

@shidel
Copy link

shidel commented Aug 16, 2024

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.

@PerditionC
Copy link
Contributor

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants