Search results

Yes, It works perfectly. I want to say thanks. If anybody has this problem just do as following instruction : 1. Creat a dataset with correct permission(maybe 775 or 777). 2.Share via NFS on freenas but pay a attention to the permission on this : Maproot User: N/A Maproot Group: N/A Mapall...

Hi Candl, i have a problem with my proxmox and Freenas like your thread. http://forum.proxmox.com/threads/16595-Cannot-mknod-Input-output-error-on-CT please help me to solve this. Thanks

Thanks Mir, But there is no option to change the group owner to root. The group is not valid And I tried to edit by command line in the SAN BOX: [root@freenas]chown -R root:root /mnt/vol1/images-nfs and i received "Chown root invalid argument"

Hi Raymond, I have the same problem like you and i have not found any solutions jet. Could you please share me your configuration files. I also have a thread here : http://forum.proxmox.com/threads/19270-OpenVZ-Container-on-NFS-Share-error-with-exit-code-48

Re: tar. cannot change ownership to uid 0,gid 0; permission denied when creating a Op The same problem with proxmox V3.2 when using freenas 8.3 via NFS share (Datasets were set to 777). How can i fix this issue ? I have already posted a thread here...

And some pics from SAN and Proxmox Configuration files :

Yes, I have 2 datasets were set to 777.

Thanks for your help but it still has this error. Do i have to add a no_root_squash to /etc/export I have already tried this but was not successful.

Yes, No above exit code 48 error but new error: I am trying to fix. But after restart the Proxmox Cluster i saw the error exit code 48 again The config in /etc/pve/storage.cfg still left :

I cannot create an OpenVZ Container within my NFS Store. I have created several KVM's within the store without any problems. The error code upon creation of the container using a template downloaded from the store Creating container private area...

Solved!