Sorry if this is more a PostgreSQL problem, or a VirtualBox problem. Makes sense so far.ĬREATE DATABASE "recurring_docs_plus_automation_linwork5"ĮRROR: could not fsync file "pg_tblspc/263215/PG_9.5_201510051/273398": Invalid argument If (in nautilus) I open that symlink I sure enough see the PG_9.5_201510051 folder, which is empty. This is actually a symlink to /media/sf_LinWork5/test-tablespace. In the VM, I go to /var/lib/postgresql/9.5/main/pg_tblspc and find a folder called 263215. And in that folder it creates another folder called PG_9.5_201510051. I had to pre-create the folder test-tablespace.
LOCATION '/media/sf_LinWork5/test-tablespace' Yes, it was easier to use an EXT4 file system. I tried to use pgadmin3 to create a tablespace on the vbox shared folder because it is large enough to hold all my data, but it doesn't work due to a permissions problem.ġ.) does it matter, regards permissions, that this vbox shared folder is an NTFS file system?Ģ.) which level are the permissions enforced, Host, VM or both?ģ.) even though my VM user account has full access to the vbox shared folder why can't pgadmin create the datastore folders and files?Ĥ.) how do I change permissions on NTFS file systems and at what level, Host, VM or both? Maybe it would be easier to use an EXT4 file system? It is an out-of-the box all-in-one deb package and it creates the Postgres datastore inside the VM - on the virtual disk file. I have no problem, when logged into the VM, to read, write create, delete, etc folders and files on the vbox shared folder.
I have defined an NTFS vbox shared folder of a large partition different from where the host is and from where the virtual disk file is located.
0 kommentar(er)
