Posting this in hope that someone might be able to provide some guidance (also posted on the Postgres mailing list and got some suggestions that didn't solve my issue).
Have been putting together a VM with a bunch of tools, including Postgres, on an Ubuntu 10.04 LTS guest OS for some time now. Recently we upgraded to Workstation 10 and have been using this as a base to update and build a new VM that is distributed to our users. Unfortunately it looks like the upgrade to Workstation 10 has caused some issues in Postgres that we did not see before. Our host OS' are Redhat 5.9 and it looks like the issues I am running to stem from running Postgres (and its data directory) out of a shared folder. The initdb step of postgres fails with the following error (snippet below):
DEBUG: TZ "posix/Universal" gets max score 5200
DEBUG: TZ "posix/W-SU" scores 0: at 1389225600 2014-01-09 04:00:00 std versus 2014-01-09 00:00:00 std
DEBUG: TZ "posix/GMT-0" scores 0: at 1389225600 "GMT" versus "UTC"
DEBUG: TZ "posix/GB" scores 0: at 1389225600 "GMT" versus "UTC"
DEBUG: TZ "posix/EST5EDT" scores 0: at 1389225600 2014-01-08 19:00:00 std versus 2014-01-09 00:00:00 std
DEBUG: TZ "posixrules" scores 0: at 1389225600 2014-01-08 19:00:00 std versus 2014-01-09 00:00:00 std
DEBUG: TZ "localtime" gets max score 5200
DEBUG: TZ "W-SU" scores 0: at 1389225600 2014-01-09 04:00:00 std versus 2014-01-09 00:00:00 std
DEBUG: TZ "GMT-0" scores 0: at 1389225600 "GMT" versus "UTC"
DEBUG: TZ "GB" scores 0: at 1389225600 "GMT" versus "UTC"
DEBUG: TZ "EST5EDT" scores 0: at 1389225600 2014-01-08 19:00:00 std versus 2014-01-09 00:00:00 std
DEBUG: invoking IpcMemoryCreate(size=29278208)
DEBUG: creating and filling new WAL file
LOG: could not link file "pg_xlog/xlogtemp.4163" to "pg_xlog/000000010000000000000000" (initialization of log file 0, segment 0): Operation not permitted
FATAL: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory
DEBUG: shmem_exit(1): 3 callbacks to make
DEBUG: proc_exit(1): 3 callbacks to make
DEBUG: exit(1)
DEBUG: shmem_exit(-1): 0 callbacks to make
DEBUG: proc_exit(-1): 0 callbacks to make
child process exited with exit code 1
I can run the initdb step on the VM and install to a non-shared folder directory (i.e. /tmp/) and do not run into any issues. I had thought it might be tied to an older version of vmware-tools (we were manually installing an 8.x version of vmware-tools) so I went ahead and installed the 9.6.x version of vmware-tools and on one of my test machines running Workstation 10 everything worked out perfectly. I replicated the process on a machine running Workstation 9 and it still failed. So I am not sure if some fixes in Workstation 10 are taking care of the problem that are not present in Workstation 9 but we have users who are using older versions of Workstation, Player and Fusion so having them update to a newer version isn't an optimal solution for us.
Any help would be appreciated.