Hi-
New to the forums- I have a new FreeNAS server that we would like to use as a main fileserver, replacing 3 Linux fileservers. I have 4 iXSystems FreeNAS minis that work fine. This main fileserver appears to be set up identically, but regardless of the mechanism I use to copy (rsync, cp, tar) I keep getting permission problems, especially with our version control files (git and mercurial, w/.git and .hg dirs respectively) This is how the system is set up:
FreeNAS version:
OS Version:
FreeNAS-11.2-U5
(Build Date: Jun 24, 2019 18:41)
Processor:
Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz (32 cores)
Memory:
128 GiB
Sharing is configured thusly:
All Dirs
Authorized hosts and networks left blank for all
Maproot user is set to root
Maproot Group is set to wheel
Pool is set to:
Sync = standard
compression level = lz4 (recommended)
Share Type= Unix
No quotas are set
Dedup is off
Read Only is off
Excec is On
Auth is set to sys
users/groups is served via NIS, and users and groups show up properly
# Mounting from host is:
mount -t nfs -o rw,hard,rsize=8192,wsize=8192,timeo=14,intr,tcp server:/mnt/mount-point /tmp/mount-point
However, when copying or rsync directories from the source fileserver to the new FreeNAS fileserver, I get:
cp: preserving permissions for ‘./modules/cadence’: Operation not permitted
cp: preserving permissions for ‘./modules/include’: Operation not permitted
rsync: mkstemp "/tmp/nas-001-vol-01/config/config/modules/mentor/calibre/.common.0.7q6ei3" failed: Operation not permitted (1)
rsync: mkstemp "/tmp/nas-001-vol-01/config/config/modules/mentor/calibre/.version.VqiXiy" failed: Operation not permitted (1)
I have the same issues for tar with the same error. I just need to make sure I doing something equivalent to "no_root_squash".
This all works properly if I go from a Linux fileserver to Linux fileserver, or to a Netapp.
What am I missing? Do I need to define a root host? I'm combining 3 older Linux fileserver onto a FreeNAS server. Or was trying to anyway.
We were planning on moving everything this weekend, but if I don't get this solved that won't happen, and I'll have to use an old Netapp instead.
New to the forums- I have a new FreeNAS server that we would like to use as a main fileserver, replacing 3 Linux fileservers. I have 4 iXSystems FreeNAS minis that work fine. This main fileserver appears to be set up identically, but regardless of the mechanism I use to copy (rsync, cp, tar) I keep getting permission problems, especially with our version control files (git and mercurial, w/.git and .hg dirs respectively) This is how the system is set up:
FreeNAS version:
OS Version:
FreeNAS-11.2-U5
(Build Date: Jun 24, 2019 18:41)
Processor:
Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz (32 cores)
Memory:
128 GiB
Sharing is configured thusly:
All Dirs
Authorized hosts and networks left blank for all
Maproot user is set to root
Maproot Group is set to wheel
Pool is set to:
Sync = standard
compression level = lz4 (recommended)
Share Type= Unix
No quotas are set
Dedup is off
Read Only is off
Excec is On
Auth is set to sys
users/groups is served via NIS, and users and groups show up properly
# Mounting from host is:
mount -t nfs -o rw,hard,rsize=8192,wsize=8192,timeo=14,intr,tcp server:/mnt/mount-point /tmp/mount-point
However, when copying or rsync directories from the source fileserver to the new FreeNAS fileserver, I get:
cp: preserving permissions for ‘./modules/cadence’: Operation not permitted
cp: preserving permissions for ‘./modules/include’: Operation not permitted
rsync: mkstemp "/tmp/nas-001-vol-01/config/config/modules/mentor/calibre/.common.0.7q6ei3" failed: Operation not permitted (1)
rsync: mkstemp "/tmp/nas-001-vol-01/config/config/modules/mentor/calibre/.version.VqiXiy" failed: Operation not permitted (1)
I have the same issues for tar with the same error. I just need to make sure I doing something equivalent to "no_root_squash".
This all works properly if I go from a Linux fileserver to Linux fileserver, or to a Netapp.
What am I missing? Do I need to define a root host? I'm combining 3 older Linux fileserver onto a FreeNAS server. Or was trying to anyway.
We were planning on moving everything this weekend, but if I don't get this solved that won't happen, and I'll have to use an old Netapp instead.