The client will see the full, long file name, although looking different.
When files created via NFS contain illegal characters, the charmap command can be used to set up a translation table to present an alternative display of such characters to CIFS clients. Configuring alternative presentation of illegal characters. #Nfs client software for windows 10 professional
Shown here on Windows XP Professional with SP2:. Both XP and NetApp will name the files in order of last modified date with regard to the ~1 part of the naming scheme while NetApp will remove the numbering after the limit of 5 is reached. The limit is 5 file or directories with duplicate character sets in the first 8 characters of the 8.3 naming scheme. The dir/x cmd on NetApp randomizes the names after the limit is reached, while on an XP directory the first two characters remain. It should be noted that the DOS emulation on NetApp is different than on Windows XP. When the client supports only 8.3 names, this new name will no longer have an equivalent in long format. The filer then receives instructions to delete the original file and create a new one. Some applications rename the original file, then save the edited file as if it were newly created. This can occur as a consequence of the way an application saves a file that it has edited. Note : Under some circumstances, an application running on a client that uses names in 8.3 format can lose the file's original long-format name. On Windows 95 and Windows NT clients, you can choose to display the short name or the long name by using File Properties. The short names are not visible to NFS clients. The short names appear on clients that support only the 8.3 format. For example, if the UNIX client creates another file named specifications_new.html, the short version of specifications_new.html is specif~1.htm. If this short name already exists, the storage system uses a different number at the end of the file name. For example, if an NFS client creates a file named specifications.html, the short name created by the storage system is specif~0.htm. It is not for showing the order of file creation. Note: The number or letter appended to the short name ensures that the file name is unique. It truncates the file name extension to three characters. If it runs out of letters and numbers because there are too many similar names, it creates a unique file name that bears no relation to the original file name. 
It appends a tilde (~) and a number or letter to the name.It truncates the file name to six characters.
The storage system generates the 8.3 name as follows:
In any directory that has access from a CIFS client, the storage system creates and maintains two names: the original long name and an additional short name in 8.3 format.
Some CIFS clients, such as MS-DOS and Windows 3.x clients, support only file names in the 8.3 format (8 characters for the file name and 3 characters for the file name extension). With an existing path of 205 characters, a new file name can only be up-to 50 characters). Note: The file name length is limited by the length of the names in the files path, (e.g. On the storage system, the maximum length of a file name is 255 characters for NFS clients and CIFS clients that support PC's long file name format. For example, file names are case-sensitive for clients running UNIX operating systems, and are case-insensitive for clients running any Windows operating systems. File naming conventions depend on both the clients' operating systems and the file-sharing protocols. File naming conventions for files that are used by both NFS and CIFS.
0 kommentar(er)
