This will be a little long so bear with me.
Brand new FreeNAS boxes, both identical. Both running 9.3. Box 1 is the file server, box 2 is the replication server. Setup went perfectly, snapshotting works, replication works.
Box 1 is bound to AD. That was a big of a pain to get working but it was on our end, dns actually, and not the freenas box. I have 1 single volume, Volume1, permissions are owner is DOMAIN\administrator, group is DOMAIN\domain admins. Right now I have a single share, Volume1.
These boxes are replacing an existing server 2008 r2 server. The first round I used syncback to copy over the 8tb of files. Everything seemed ok. All the pc, macs, linux machines could read and write. We found out later that all the macs could not open and modify any of the existing files. They were all locked.
So after hunting around and talking to a few people seems that syncback breaks "something" with permissions that the macs don't like. I was told to either copy them through a mac, or use robocopy. I chose robocopy.
This was my copy string.
robocopy z:\ y:\ /MIR /COPY:DATSO /XD "$RECYCLE.BIN"\
Right off the bat it failed. I had to remove the A flag...
Copy ran for awhile then failed on the O flag, due to files on the source server being owned by a local admin and the FreeNAS box not knowing what that was.
Finally went with.
robocopy z:\Photos y:\Photos /MIR /COPY:DTS /XD "$RECYCLE.BIN"\
This worked. So I started the copy on Saturday morning and as of today I had enough stuff over to test.
All the files are locked again by the macs. I just don't get it.
I'm posting this to FreeNAS in hopes that someone else has an idea here. This should be a simple exercise, but I'm about lost. There has to be a way to successfully copy over to FreeNAS and use that as a cifs share.
EDIT 1: Somehow the read only flag seems to get set no matter what when we copy.. just some more information
EDIT2: copied everything over through a mac. All files are still locked. This is a problem with FreeNAS. I'm sort of a loss here. My next step will be to remove all AD integration and just allow all access..
Brand new FreeNAS boxes, both identical. Both running 9.3. Box 1 is the file server, box 2 is the replication server. Setup went perfectly, snapshotting works, replication works.
Box 1 is bound to AD. That was a big of a pain to get working but it was on our end, dns actually, and not the freenas box. I have 1 single volume, Volume1, permissions are owner is DOMAIN\administrator, group is DOMAIN\domain admins. Right now I have a single share, Volume1.
These boxes are replacing an existing server 2008 r2 server. The first round I used syncback to copy over the 8tb of files. Everything seemed ok. All the pc, macs, linux machines could read and write. We found out later that all the macs could not open and modify any of the existing files. They were all locked.
So after hunting around and talking to a few people seems that syncback breaks "something" with permissions that the macs don't like. I was told to either copy them through a mac, or use robocopy. I chose robocopy.
This was my copy string.
robocopy z:\ y:\ /MIR /COPY:DATSO /XD "$RECYCLE.BIN"\
Right off the bat it failed. I had to remove the A flag...
Copy ran for awhile then failed on the O flag, due to files on the source server being owned by a local admin and the FreeNAS box not knowing what that was.
Finally went with.
robocopy z:\Photos y:\Photos /MIR /COPY:DTS /XD "$RECYCLE.BIN"\
This worked. So I started the copy on Saturday morning and as of today I had enough stuff over to test.
All the files are locked again by the macs. I just don't get it.
I'm posting this to FreeNAS in hopes that someone else has an idea here. This should be a simple exercise, but I'm about lost. There has to be a way to successfully copy over to FreeNAS and use that as a cifs share.
EDIT 1: Somehow the read only flag seems to get set no matter what when we copy.. just some more information
EDIT2: copied everything over through a mac. All files are still locked. This is a problem with FreeNAS. I'm sort of a loss here. My next step will be to remove all AD integration and just allow all access..
Last edited:
