SOLVED Replicated data from old server to new... SMB permissions on new server not working

[digilink]

I am in the process of moving all of my data from my old server to a new one, and I figured the best way to go about it was to setup a snapshot/replication task. I successfully replicated a couple of my datasets to the new server, but I now appear to be having a permissions issue on the new server.

I added the same user and made sure the workgroup was set to the same as the old server (this is a non AD environment) and while I can read in the share, I am unable to write, despite my user having full access in the permissions tab of the share, for example:

And here is how my dataset permissions are set:

If I try to create a new folder as an example, this is what I'm met with:

Would I be better off manually copying or rsync'ing the data instead to a new manually created share, or do I maybe have something implemented wrong on the new server? I did try removing and re-adding the permissions from my windows box as well as on the server itself with no luck.

 

[anodos]

I am in the process of moving all of my data from my old server to a new one, and I figured the best way to go about it was to setup a snapshot/replication task. I successfully replicated a couple of my datasets to the new server, but I now appear to be having a permissions issue on the new server.

I added the same user and made sure the workgroup was set to the same as the old server (this is a non AD environment) and while I can read in the share, I am unable to write, despite my user having full access in the permissions tab of the share, for example:

And here is how my dataset permissions are set:

If I try to create a new folder as an example, this is what I'm met with:

Would I be better off manually copying or rsync'ing the data instead to a new manually created share, or do I maybe have something implemented wrong on the new server? I did try removing and re-adding the permissions from my windows box as well as on the server itself with no luck.

Make sure your dataset isn't set to "readonly" The command to check it is zfs get readonly Pool/Dataset

 

[digilink]

Make sure your dataset isn't set to "readonly" The command to check it is zfs get readonly Pool/Dataset

That was it, thank you! For anyone in the future that may run into this, here's what I did:

Code:

[root@freenas] ~# zfs get readonly sndata-z1/stephen
NAME			   PROPERTY  VALUE   SOURCE
sndata-z1/stephen  readonly  on	  local

Change the readonly property to "off":

Code:

[root@freenas] ~# zfs set readonly=off sndata-z1/stephen

[root@freenas] ~# zfs get readonly sndata-z1/stephen
NAME			   PROPERTY  VALUE   SOURCE
sndata-z1/stephen  readonly  off	 local

I can now read/write to the share as expected :)