#Path Alias on FAS

1 messages · Page 1 of 1 (latest)

vernal mulch
#

Hey, we have some problems opening PDF's with Adobe. I just realized the Netapp CIF share doesnt create any alias for the path. Same path structure works on other Linux based CIF shares. Is there any ways to make that happen? ty

#

FAS2650 on the latest ONTAP/Firmware

void sierra
#

what do you mean by "path alias"? NetBIOS alias? If so, you have to set these manually on the CIFS server (vserver cifs add-netbios-aliases)

vernal mulch
#

no.. like:
\ArchivNAS1\Archiv\test\testtetstesttetstesttetstesttetstesttetstesttetstesttetstesttetstesttetstesttets\testtetstesttetstesttetstesttetstesttetstesttetstesttetstesttets\testtetstesttetstesttetstesttetstesttets\Neuer OrdnerNeuer OrdnerNeuer\test\testtetstesttetstesttetstesttetstesttetstesttetstesttetstesttetstesttetstesttets\testtetstesttetstesttetstesttetstesttetstesttetstesttetstesttets\testtetstesttetstesttetstesttetstesttets\Neuer OrdnerNeuer OrdnerNeuer>
becomes:
\ArchivNAS1\Archiv\test\TXQ00K~X\T7WFT5~X\TXCY6N~J\NW6PFP~Q\test\TXQ00K~X\T7WFT5~X\TXCY6N~J\NW6PFP~Q

#

@void sierra this is necessary to open files beyond the 260 character limit without using an API

void sierra
#

okay, sorry, can't help you there, I never encountered this issue before. I didn't know Samba did something crazy like that 😄
did you try the recently added registry key where Windows Explorer can support longer paths?

vernal mulch
#

yea ofc

#

i created a ticket. Hopefully someone can solve it

void sierra
#

usually when our customers have path length issues we suggest they either a) shorten the path by renaming directories or b) create a CIFS share further down the chain so that the resulting path is shorter 🤷‍♂️ I'm not aware of any setting that forces ONTAP to switch to short paths

#

I assume the SVM has -is-search-short-names-enabled true ? That's the only option I know that involves 8.3 names

vernal mulch
#

idk actually.. what is the full command? @void sierra

void sierra
#

vserver cifs options modify -vserver XXX -is-search-short-names-enabled true I think? Sorry, I can't check right now

jagged cradle
#

There are policies you can set in windows 10+ that allow greater than 260 characters in a file path as well

vernal mulch
jagged cradle
#

I use it in prod and have tested it myself, is it applying properly to that workstation/server you're testing from?

vernal mulch
#

Synology, Windows Server, Linux.. you name it

jagged cradle
#

What's the name of the policy your talking about?

vernal mulch
#

im talking about convertig the path into the 8.3 format

#

it doesnt happen

void sierra
vernal mulch
void sierra
#

yeah, I don't think I properly understood what you want the system to do, sorry, I can't help you there

vernal mulch
#

well.. on a long path it should change the path from:

hallooooooooooo\hello\tesssst\file.pdf

to

halloo~1\hello\tessss~1\file.pdf

#

this doesnt happen on the share we use

#

but it does on a new SMB share i created

void sierra
#

what do you mean "change the path"? if the client requests a long path it should change that to a short path? or do you want it to create 8.3 names for every file? because I think the former is not possible while the latter works

#

is the new share in the same SVM?

vernal mulch
#

i want it to create a 8.3 paths

void sierra
#

then it's a share property probably

#

if it's in a different SVM I would check and compare CIFS options

void sierra
# vernal mulch i want it to create a 8.3 paths

it creates 8.3 filenames. if the client requests "\foo\looooooooooooooooong\naaaaaaaame.pdf" it uses long names. If the client requests "\foo\looo~1\naaa~1.pdf" it will get the same file

vernal mulch
#

yea.. this doesnt work on my old share

#

but it does on a new one

void sierra
#

same svm or different svm?

vernal mulch
#

same svm

void sierra
#

did you check the share properties?

vernal mulch
#

different volume / share

void sierra
#

also compare volume options

#

there is probably a difference somewhere

vernal mulch
#

i cannot spot any (at least on the ONTAP System Manager)

void sierra
#

yeah, no, I don't think you will have any luck with the System Manager there, you probably need to check on the CLI

vernal mulch
#

well... i tried some commands but couldnt see any difference between the shares. i can post some stats tomorrow

vernal mulch
#

it took some time.. i tested it right away after the command

#

it seems like, it needs some time to creat the alias names