>Number:         5468
>Category:       kern
>Synopsis:       msdosfs: mv of a file to a preexisting file loses long filename
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 19 20:35:00 1998
>Last-Modified:
>Originator:     Dave Huang
>Organization:
Name: Dave Huang     |   Mammal, mammal / their names are called /
INet: khym@bga.com   |   they raise a paw / the bat, the cat /
FurryMUCK: Dahan     |   dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 22 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++
>Release:        NetBSD-current as of May 18, 1998
>Environment:
	
System: NetBSD dahan.metonymy.com 1.3E NetBSD 1.3E (SPIFF) #219: Tue May 19 20:28:28 CDT 1998 khym@dahan.metonymy.com:/usr/src.local/sys/arch/i386/compile/SPIFF i386


>Description:
	On a msdos filesystem with Win95 long filenames enabled, if
you mv a file on top of an existing file, the destination file will
lose its long filename (if it has one).
>How-To-Repeat:
% touch a longfilename
% ls
a            longfilename
% mv a longfilename
% ls
LONGFI~1

>Fix:
	I don't know... but I do know that the long filename entry is
still there and looks fine, it's just been marked as deleted (the
first byte is 0xe5). The removede(zp, ip) at line 1154 of
msdosfs_vnops.c looks kinda fishy to me; wasn't ip just createde()'d a
few lines above that?
>Audit-Trail:
>Unformatted: