vmhgfs-fuse is mostly ignorant to upper and lower case filenames

may a more illustrative test is:

ls -l test TEST; touch test; ls -l test TEST; ls -l | grep -i test
ls: cannot access 'test': No such file or directory
ls: cannot access 'TEST': No such file or directory
-rwxrwxrwx 1 root root 0 Mai 12 20:19 test
-rwxrwxrwx 1 root root 0 Mai 12 20:19 TEST
-rwxrwxrwx 1 root root 0 Mai 12 20:19 test

rm test

ls -l test TEST; touch TEST; ls -l test TEST; ls -l | grep -i test
ls: cannot access 'test': No such file or directory
ls: cannot access 'TEST': No such file or directory
-rwxrwxrwx 1 root root 0 Mai 12 20:19 test
-rwxrwxrwx 1 root root 0 Mai 12 20:19 TEST
-rwxrwxrwx 1 root root 0 Mai 12 20:19 TEST

so the file gets created with the right upper and lowercase-ing but it can be accessed and deleted either way (lower or upper case)

Hi there,

I am the developer for the file sharing Shared Folders feature, and many thanks for reporting this issue.

Can you please confirm the product you are using and version together with the details of the host system you are running the product on.
It will help with bug filing and verification here at VMware.

Thanks
Steve

hi,

this is on VMware Workstation 12.1.1 in a win7 64bit host.

Regards

Ulf

> On 13.05.2016, at 20:14, "<email address hidden>" <email address hidden> wrote:
>
> Hi there,
>
> I am the developer for the file sharing Shared Folders feature, and many
> thanks for reporting this issue.
>
> Can you please confirm the product you are using and version together with the details of the host system you are running the product on.
> It will help with bug filing and verification here at VMware.
>
> Thanks
> Steve
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1581164
>
> Title:
> vmhgfs-fuse is mostly ignorant to upper and lower case filenames
>
> Status in open-vm-tools package in Ubuntu:
> New
>
> Bug description:
> Hi,
>
> vmhgfs-fuse doesnt seem to care much for upper and lower case usage in
> filenames but represents the file just the way it likes.
>
> to reproduce:
>
> ls -l TEST test; touch test; ls -l test; ls -l TEST; touch TEST; ls -l
> TEST; rm TEST; ls -l TEST; sleep 6; ls -l test TEST
>
> ls: cannot access 'TEST': No such file or directory
> ls: cannot access 'test': No such file or directory
> -rwxrwxrwx 1 root root 0 Mai 12 20:04 test
> -rwxrwxrwx 1 root root 0 Mai 12 20:04 TEST
> -rwxrwxrwx 1 root root 0 Mai 12 20:04 TEST
> -rwxrwxrwx 1 root root 0 Mai 12 20:04 TEST
> ls: cannot access 'test': No such file or directory
> ls: cannot access 'TEST': No such file or directory
>
> which is:
> - make sure none of the two files exists
> - create lowercase file
> - prove that lowercase got created: good
> - prove that uppercase is still not their: FAIL (its there magically)
> - create uppercase file
> - prove uppercase file got created: good (kind of, the file was already there)
> - remove uppdercase file
> - prove that uppercase file was removed: FAIL (its still there)
> - wait for things to settle
> - prove that lowercase file wasnt harmed: FAIL (lowercase file gone)
>
> Please investigate (this was working fine with vmhgfs kernel module).
>
> Thanks
>
> Ulf
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: open-vm-tools-desktop 2:10.0.7-3227872-2ubuntu1
> ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
> Uname: Linux 4.4.0-22-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2
> Architecture: amd64
> Date: Thu May 12 19:55:20 2016
> InstallationDate: Installed on 2016-01-08 (125 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> SourcePackage: open-vm-tools
> UpgradeStatus: Upgraded to xenial on 2016-05-12 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1581164/+subscriptions

Status changed to 'Confirmed' because the bug affects multiple users.

Hi there Ulf,

I don't see any difference in behavior between the vmhgfs kernel client or using the vmhgfs-fuse client in various tests I have run using my Ubuntu VMs against a Windows host.

The behavior you have described is expected given that the Windows host has case insensitive file systems.

Can you elaborate with some details and information for the case where you stated that it worked?
(Please give the Ubuntu VM version and kernel version details and version of VMware tools (output from "vmware-toolbox-cmd -v".)

Thanks.
Steve