Seagate NFS storage not working

bhagat.sameer

New Member
Sep 9, 2014
5
0
1
Hi,

We got 4 x Proxmox nodes and 1 x Seagate Enterprise (NAS OS) NFS share. I have configured NFS drive for Images, ISO, Templates, Containers and backup. When i am downloading the template to the drive there is no permission issue but when i try to create CT i get below errors.

Creating container private area (/mnt/pve/serverstorage/template/cache/ubuntu-12.04-standard_12.04-1_i386.tar.gz)
tar: ./run/.run-transition: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./run: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/libperl.so.5.14: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/lua.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/gfxboot.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/cpuid.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/whichsys.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/host.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: .: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Exiting with failure status due to previous errors
vps-create ERROR: Unpack /mnt/pve/serverstorage/template/cache/ubuntu-12.04-standard_12.04-1_i386.tar.gz failed
Creation of container private area failed


Below is my /etc/pve/storage.cfg.
dir: local
path /var/lib/vz
content images,iso,vztmpl,backup,rootdir
maxfiles 0


nfs: serverstorage
path /mnt/pve/serverstorage
server IP_Address
export /shares/proxmox/servers
options vers=3,noacl
content images,iso,vztmpl,rootdir,backup
maxfiles 100

Permission on my Seagate storage is also 0777 for all the folders. Does anyone has same issue?

Thanks
 
Hello bhagat

Creating container private area (/mnt/pve/serverstorage/template/cache/ubuntu-12.04-standard_12.04-1_i386.tar.gz)
tar: ./run/.run-transition: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./run: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/libperl.so.5.14: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/lua.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/gfxboot.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/cpuid.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/whichsys.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: ./usr/lib/syslinux/host.c32: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: .: Cannot change ownership to uid 0, gid 0: Operation not permitted
tar: Exiting with failure status due to previous errors
vps-create ERROR: Unpack /mnt/pve/serverstorage/template/cache/ubuntu-12.04-standard_12.04-1_i386.tar.gz failed
Creation of container private area failed

...........


Permission on my Seagate storage is also 0777 for all the folders. Does anyone has same issue?

Yes, I had. Solved the problem by adding in the NFS server in file /etc/exports "no_root_squash", e.g. like this

Code:
/nfsshare    10.1.0.0/255.255.0.0(rw,async,[COLOR=#ff0000]no_root_squash[/COLOR])

Success!

Mr.Holmes
 
Hi Holmes,

Thanks very much for your advice. Unfortunately i dont have SSH access to the Seagate NAS storage. I called the support and they mentioned that their current NAS OS Firmware 3.2.7.1 does not support SSH. But the new release will which will be released end of this month.:mad:

Is there any alternate work around or i just need to wait for the seagate to release the new firmware?

Again thanks for helping me out.