Savell Martin
Contributor
- Joined
- Jun 10, 2013
- Messages
- 164
Anyone?
I have the opportunity to move my data off my FreeNAS server (as im still in the process of setting it up).
My question is, would it be better to download and do a totally clean install of 9.2.1 rather than upgrading from 9.2?
As in re-create new clean volumes and everything with the new Release?
Or is there no difference with upgrading?
Can anyone help with this?
Is it a bug should I file it or is it expected?
Just I get it all day every day:
Feb 13 08:18:44 freenas smbd[56971]: [2014/02/13 08:18:44.136704, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 13 08:18:44 freenas smbd[56971]: matchname: host name/name mismatch: 192.168.1.8 != (NULL)
Feb 13 08:18:44 freenas smbd[56971]: [2014/02/13 08:18:44.136745, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 13 08:18:44 freenas smbd[56971]: matchname failed on 192.168.1.8
Feb 13 08:24:14 freenas smbd[57212]: [2014/02/13 08:24:14.128032, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 13 08:24:14 freenas smbd[57212]: matchname: host name/name mismatch: 192.168.1.17 != (NULL)
Feb 13 08:24:14 freenas smbd[57212]: [2014/02/13 08:24:14.128131, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 13 08:24:14 freenas smbd[57212]: matchname failed on 192.168.1.17
I would really like to try 9.2.1 but the CIFS read-only problems are scaring me off.
find /mnt/path_to_share/ -type d -exec setfacl -m owner@:full_set:fd:allow,group@:modify_set:fd:allow {} \;
find /mnt/path_to_share/ -type f -exec setfacl -m owner@:full_set::allow,group@:modify_set::allow {} \;
it's due to SAMBA4 and ACLs. there's already a workaround in the bug ticket. I implimented it on my system and now no longer have the issue:
check out posts #17 and #25
https://bugs.freenas.org/issues/4151
To update permissions recursively for folders:
Code:find /mnt/path_to_share/ -type d -exec setfacl -m owner@:full_set:fd:allow,group@:modify_set:fd:allow {} \;
and for files:
Code:find /mnt/path_to_share/ -type f -exec setfacl -m owner@:full_set::allow,group@:modify_set::allow {} \;
i only ran the command for permissions recursively for folders. i did not have a need to run it for my files. after that, i had the access and rights required for my needs.
IMHO, when you create a dataset in the GUI, assign it an owner and group, then just create a share of that drive it should just work as the user intended.
Not have to fire a command line and manually play with the ACL
Updated by John Hixson about 18 hours ago
So, everyone that is following this ticket: samba4 is more finicky about ACL's then previous versions were. Several people have posted how to address this issue moving forward. It is unfortunate that this came about, but there are workarounds. Moving forward, default ACL's that are reasonable have been committed to FreeNAS and will be available in 9.2.1.1. I consider this ticket as "behaves correctly". For any of you that are having this issue, please read the ticket in full for the various methods to address this issue. It's not really a "bug", just "changed behavior".
- Status changed from Investigation to Behaves correctly