Question on short/mangled file name.

[Jeremy Allison]

On Thu, Oct 02, 2014 at 10:08:55AM +0200, Volker Lendecke wrote:
> On Wed, Oct 01, 2014 at 06:35:21PM -0700, Hemanth Thummala wrote:
> > Regarding client behavior, one of our customer reported an issue saying
> > software installation in his client workstation is failing with error
> > "Error 1325: 'Favorites' is not a valid short name". He is getting this
> > error when he sets the registry settings for Favorites as our server home
> > directory path (ex: \\server\share\testusername\favorites). This error is
> > not seen when he sets the path as  \\server\share\<samba generated short
> > name for "test user">\<samba generated short name for "favorites">. Based
> > on this I assume that client would have expected short name in window
> > style. When its specified explicitly, its started working fine. If we have
> > generated short name in windows style, client would have not thrown this
> > error. I agree that I assumed few things here. But would like to understand
> > why our short file names are not in windows style.
> 
> The main reason is I believe that Samba generates them
> on-the-fly and does not store them anywhere. Windows stores
> them in NTFS, Samba does not. We could in theory put that
> into an xattr, but right now we don't.

At least for hash2 we shouldn't have to store them
as they are algorithmicly generated from the
(uppercased) incoming filename.