Handling of 8,3 names on a NetApp

[Richard Sharpe]

On Tue, 3 Dec 2002, Simo Sorce wrote:

> seem a poor hashing algorithm like the one present in w2k.
> Simo.

Yes. It is interesting, in that Win2K produces what look like line noise 
one file earlier:

smb: \funny\> altname funnyfilea.txt
FUNNYF~1.TXT
smb: \funny\> altname funnyfileb.txt
FUNNYF~2.TXT
smb: \funny\> altname funnyfileb.txt
FUNNYF~2.TXT
smb: \funny\> altname funnyfilec.txt
FUNNYF~3.TXT
smb: \funny\> altname funnyfiled.txt
FUNNYF~4.TXT
smb: \funny\> altname funnyfilee.txt
FU8DED~1.TXT
smb: \funny\> altname funnyfilef.txt
FU8DE1~1.TXT

I wonder what NT does? I guess I will find out.
 
> On Tue, 2002-12-03 at 07:19, Richard Sharpe wrote:
> > Hi,
> > 
> > It seems that netapp generates something approaching line noise for 8,3 
> > names after a certain number of names that differ after char 8 have been 
> > created:
> > 
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalong.fil
> > THISIS~1.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalona.fil
> > THISIS~2.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalonb.fil
> > THISIS~3.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalonc.fil
> > THISIS~4.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalond.fil
> > THISIS~5.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalone.fil
> > ~CVWO000.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalonf.fil
> > ~DVWO000.FIL
> > smb: \usr10\home\rsharpe\ntap\> altname thisisalonh.fil
> > ~EVWO000.FIL
> > 
> > 
> > 
> > Regards
> > -----
> > Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
> > sharpe[at]ethereal.com, http://www.richardsharpe.com
> 

-- 
Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com