vboxsf filesystem doesn't handle no extension file name

[Arirang]

I am using VirtualBox version 5.2.20. My virtual machine (Ubuntu Linux) is running Windows 10. I set up shared folders and it mounted with -t vboxsf on the Ubuntu.

Here is error case with vboxsf filesystem: I created ".new.test1." file but it created ".new.test1" file.

chwon@chwon-VirtualBox:~/sandbox/tmp$ echo "hello" > .new.test1.
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls -la
total 5
drwxrwxrwx 1 chwon chwon    0 Nov  8 15:12 .
drwxrwxrwx 1 chwon chwon 4096 Nov  8 15:11 ..
-rwxrwxrwx 1 chwon chwon    6 Nov  8 15:12 .new.test1
chwon@chwon-VirtualBox:~/sandbox/tmp$ 
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1.
ls: cannot access .new.test1.: No such file or directory
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1
.new.test1

I did same test on Linux ext4 filesystem.

chwon@chwon-VirtualBox:~/tmp/test$ echo "hello" > .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls -la
total 12
drwxrwxr-x 2 chwon chwon 4096 Nov  8 15:28 .
drwxrwxr-x 4 chwon chwon 4096 Nov  8 15:28 ..
-rw-rw-r-- 1 chwon chwon    6 Nov  8 15:28 .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1. 
.new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1
ls: cannot access .new.test1: No such file or directory

[grawity]

IMHO this is normal, because Windows itself (specifically the Win32 API) forbids filenames which end in a dot and automatically removes the dot on all operations.

If Virtualbox was changed to bypass this restriction, that'd fix the Linux side but then you wouldn't be able to access .new.test1. from the Windows side...

[Arirang]

I have had this problem with recent version of VirtualBox. I don't know exactly which version.

If it removes the dot on all operations, the dot should be removed when Linux try to access it. For example, when run "cat .new.test1." on Linux, VirtualBox should remove the dot and access ".new.test1" file.

Do you know why it changed and which version changed it?

[Arirang]

Do you have any update? It looks for me this is VirtualBox problem.