Subject: kern/9991: rsync/msdosfs problem
To: None <gnats-bugs@gnats.netbsd.org>
From: None <wiz@danbala.ifoer.tuwien.ac.at>
List: netbsd-bugs
Date: 04/27/2000 04:21:21
>Number: 9991
>Category: kern
>Synopsis: rsync/msdosfs problem
>Confidential: no
>Severity: non-critical
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 27 04:22:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Wiz
>Release: tested on 1.4.2, believed to be there on -current
>Organization:
>Environment:
System: NetBSD hiro.xon.net 1.4.2 NetBSD 1.4.2 (HIRO) #3: Fri Apr 7 01:30:48 CEST 2000 wiz@hiro.xon.net:/archive/cvs/1.4.x/sys-bktr-test/arch/i386/compile/HIRO i386
>Description:
Using rsync to synchronize a file with an LFN on a msdosfs results in
loss of the file's LFN.
>How-To-Repeat:
mount /some/dos/device /disk/win98
touch somelongfilename
rsync somelongfilename /disk/win98
(this one works, because the file's not there yet)
--output
somelongfilename
wrote 80 bytes read 32 bytes 224.00 bytes/sec
total size is 0 speedup is 0.00
--end output
rsync somelongfilename /disk/win98
--output
somelongfilename
stat somelongfilename : No such file or directory
wrote 80 bytes read 32 bytes 74.67 bytes/sec
total size is 0 speedup is 0.00
--end output
The target directory then only contains a file SOMELO~1, the LFN gets
lost.
I filed this under kern because rsync works okay on non-msdosfs.
>Fix:
Sorry, don't know.
>Release-Note:
>Audit-Trail:
>Unformatted: