Problem with disk sharing after 9.0.23062 update on debian wheezy

Discussion in 'Linux Virtual Machine' started by richmit, Mar 20, 2014.

  1. richmit

    richmit Bit poster

    Messages:
    3
    Before the update everything worked. Now when any program tries to open+create a file without u+rw in a directory shared with OSX, the open system call fails with a memory error! I noticed it first with some SCM tools that create the file without read/write. I am able to duplicate the problem with the following code:

    #include <stdio.h>
    #include <unistd.h>
    #include <fcntl.h>
    #include <stdlib.h>

    int main(int argc, char *argv[]) {
    int FD;

    if((FD = open("foo", O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR)) < 0) {
    printf("First open: NO NO NO NO!!\n");
    perror(" ERROR MSG");
    } else {
    printf("First open: YES!!\n");
    } /* end if */

    close(FD);

    if((FD = open("bar", O_WRONLY | O_CREAT | O_TRUNC, S_IWUSR)) < 0) {
    printf("Second open: NO NO NO NO!!\n");
    perror(" ERROR MSG");
    } else {
    printf("Second open: YES!!\n");
    } /* end if */

    close(FD);

    if((FD = open("foobar", O_WRONLY | O_CREAT | O_TRUNC, S_IRUSR | S_IWUSR)) < 0) {
    printf("Third open: NO NO NO NO!!\n");
    perror(" ERROR MSG");
    } else {
    printf("Third open: YES!!\n");
    } /* end if */

    close(FD);

    exit(0);
    } /* end func main */

    =========================================
    Run it on a directory on the VM's disk:

    gcc t.c -o t; rm -rf foo bar foobar; ./t
    First open: YES!!
    Second open: YES!!
    Third open: YES!!

    =========================================
    Run it on a shared directory:

    gcc t.c -o t; rm -rf foo bar foobar; ./t
    First open: NO NO NO NO!!
    ERROR MSG: Cannot allocate memory
    Second open: NO NO NO NO!!
    ERROR MSG: Cannot allocate memory
    Third open: YES!!
     
    Last edited: Mar 20, 2014
  2. richmit

    richmit Bit poster

    Messages:
    3
    I just reverted to 9.0.24172, and now everything works like it did before...
     
  3. tafkaks

    tafkaks Bit poster

    Messages:
    6
  4. jskitz

    jskitz Bit poster

    Messages:
    3
    I'm having the same issue but in 9.0.24172. richmit, did you mean that you upgraded to 9.0.24172 from 9.023062?
     
  5. richmit

    richmit Bit poster

    Messages:
    3
    Sorry, i think I borked the title -- which I think I cut-n-pasted, duno how I did that. :)

    I updated 9.0.23062 to 9.0.24217.979618 and had problems. Then I got the dmg for 9.0.24172.951362, and that fixed things. I am now running this 24172 on both my desktop and laptop, and all is working.
     
    Last edited: Mar 24, 2014
  6. jskitz

    jskitz Bit poster

    Messages:
    3
    Would you happen to have a link to the 9.0.24172.951362 dmg? I tried some URL hacking, but was not able to hit on it. The only other place I could find this version (cracked) were on torrent sites. I'm really disappointed in Parallels support and am surprised how hard they make it to just go back to a previous version. While at the same time, not responding to the threads and / or patching the problem. Especially since you did such a good job of exactly exposing the bug :) Any help you can provide would be much appreciated!
     
  7. tafkaks

    tafkaks Bit poster

    Messages:
    6
    I happened to just have my original lying around. If you're blocked, though, you can just use an nfs share from your host. The performance seems to be just as good as the Parallels share, and not buggy. It's really easy to set up:

    https://gist.github.com/mowings/9782264#file-gistfile1-md
     

Share This Page