Can't copy read only file when running an Ubuntu VM. Bug?

In my Ubuntu VM, if I'm cd'd to a dir that's shared (a dir that's native to my host OS, and mounted on the Ubuntu VM through /media/psf), I cannot copy a read-only file from one location to another. If I give the file write permissions, I can copy it. This only seems to be an issue under Ubuntu, and is only an issue with Parallels.

Here's a repeatable test:

Code:

briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ echo "test file" > foo && chmod a-w foo
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ mkdir bar
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l
[COLOR="#0000FF"]total 0
drwxr-xr-x 1 briank 68 May 22 16:52 bar/
-r--r--r-- 1 briank 10 May 22 16:52 foo[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat foo
[COLOR="#0000FF"]test file[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cp foo bar
[COLOR="#FF0000"]cp: cannot create regular file `bar/foo': Cannot allocate memory[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l bar
[COLOR="#0000FF"]total 0
-r--r--r-- 1 briank 0 May 22 16:53 foo[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat bar/foo 
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ rm -fv bar/foo
[COLOR="#0000FF"]removed `bar/foo'[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ chmod -v u+w foo
[COLOR="#0000FF"]mode of `foo' changed from 0444 (r--r--r--) to 0644 (rw-r--r--)[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cp -v foo bar/
[COLOR="#0000FF"]`foo' -> `bar/foo'[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat bar/foo 
[COLOR="#0000FF"]test file[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l bar/foo
[COLOR="#0000FF"]-rw-r--r-- 1 briank 10 May 22 16:54 bar/foo[/COLOR]

So when the permissions of "foo" don't contain the write bit, I can't copy correctly - the file gets there, but it is 0 bytes. But when foo is writable, I can copy it.

Is this a bug or some sort of setting problem? I'm running Build 9.0.24217 (Revision 979618; Tuesday, February 25, 2014)

 

Hello BrianKK,

Please update your Parallels Desktop 9 to the latest build ( 9.0.24229 ) by following the steps as suggested at http://kb.parallels.com/111603 and us know how it works!

 

With all due respect, I have a LOT of VMs (necessary for work) - it takes hours to update Parallels Tools for all of them and the automatic install only works for newer Linux distributions, which means I'm updating Parallels Tools by hand on several of them.

That said, I don't see anything here: http://kb.parallels.com/en/117225 that alludes to a solution to my problem (or Linux VMs, in general). For me, I'm only seeing this under Ubuntu - it works fine under CentOS, Fedora, and Suse VMs. Is there any indication that my problem will be solved by updating to this version?

Parallels Desktop 9 for Mac (build 9.0.24229) addresses overall stability and performance issues, and includes the following fixes:
Resolves an issue with Parallels Transporter Agent not launching on Windows computers.
Resolves an issue with Coherence view mode for Windows 8.1 Update 1 virtual machines.
Resolves an issue with jumping to the OS X login screen while working in a Windows virtual machine in Coherence mode on a MacBook Pro with Retina display.
Resolves an issue with time synchronization after resuming an OS X virtual machine.
Resolves an issue with automatic resolution while resizing an OS X Mavericks virtual machine window.
Resolves an issue with OS X virtual machines crashing when more than 64MB of video memory is allocated.
Resolves an issue with Parallels Tools features (copy and paste, and shared folders) for Mac OS X 10.5 virtual machines.​

I'm fine upgrading, but I don't want to waste half of my day (or more) for a "let's see what happens". For the record, I'm on 9.0.24217 which is, as you know, one build old.

 

I updated Parallels.

It didn't help. Same behavior as before.

Next thing to try?