defuseme2k
[H]ard|Gawd
- Joined
- Oct 7, 2004
- Messages
- 1,074
So, I got this problem... and it is interesting. NFS3 would be so much easier.. but can't get that easily through a firewall in this situation, SO, NFS4 with TCP 2049 is what I have.
My issue is I can mount just fine (old NetApp OS build, its OLD I mean 2008 old). Still, it does mount and I can write. However, I cannot chown -R my transfer directory to vcloud.vcloud. If I attempt to start the service it complains in the cell.log.
I'm no NFS guru nor NetApp (I'm FC all the way). I'm curious, for the user mapping to work correctly, do we need to create a matching user/group on the netapp with matching uid gid respectively? I think the netapp equiv to no root squash is anon=0, which we've done too. Unfortunately, I'm not driving the storage bus. Another group is.
My issue is I can mount just fine (old NetApp OS build, its OLD I mean 2008 old). Still, it does mount and I can write. However, I cannot chown -R my transfer directory to vcloud.vcloud. If I attempt to start the service it complains in the cell.log.
I'm no NFS guru nor NetApp (I'm FC all the way). I'm curious, for the user mapping to work correctly, do we need to create a matching user/group on the netapp with matching uid gid respectively? I think the netapp equiv to no root squash is anon=0, which we've done too. Unfortunately, I'm not driving the storage bus. Another group is.