CIFS file sort order

I haven't heard of any such issues. Tried working with support ?

That might be related to the name mangling from long file names to DOS M8.3

It's most likely not an issue of the VNX itself but how you copy

Also search the Parameters Guide

I think there was a param to change M83 search order - might make a difference

Searched the parameters guide, but could not find anything related to file sorting.

In this case has nothing to do with 8.3 filenames, it happens also for short file names and even directories.

The list seems simply not sorted on a VNX-File as it was on old days Windows2003 CIFS-servers.

Yes we can raise a support ticket, but as Primus doesn't have anything on this I doubt the answer...

I think I have a pretty good guess whats happening.

On Windows and VNX every file has two names - one long name (Unicode) and one short DOS M83 name (8 character name plus 3 char extention).

When you create a file with a name longer than M83 the Windows/  CIFS server will automatically create a mangled M83 name according to defined rules.

If the M83 name is already present another one with a number postfix is chosen.

When you copy files from over CIFS only the long name gets copied - the M83 name gets created on the destination.

That is because the M83 name from the the source could already be used in the destination directory.

So on a copy with long names that have mangling conflicts which specific M83 name you get for a file depends on whether that name already exists on the destination.

Even if that is not the case and if the destination uses the same mangling rules in case of multiple conflicts your actual M83 name depends on the order the files get created on the destination.

We did do some change there very recently that you can try (see below) - but you would have to copy your files again.

Or find a Windows command to remove the M83 names.

Rainer

-------------------------------------------------------------------------------------------------------------------------------

Tracking number:  531452 / 51721068

Symptom Description:

Unicode long file names that were not legal 8.3 filenames would have 8.3 filenames generated in the form filena~1.ext for the first four filenames. If ~1 through ~4 were in use .ext would be used with being any unused 8 digit or less value. Migration of files could fail if the Unicode long filename of a file to be copied matched the 8.3 generated filename of another file already copied to the same folder.

Fix Summary:

Added a new parameter ufs.mangleM83ByNumber to optionally restrict the 8.3 filename creation policy to not include ~n names.

Exists in versions:   7.1.65.8  7.1.56.5 7.1.55.3  7.1.47.5

Fixed in version:  7.1.71.1

sorry - thats an undocumented param to not report short names in directory enumeration.

If you want to try this ask support for permission and usage of cifs.M83search

Rainer