Migration to FreeNAS / Moving the file

BlazeStar · Nov 17, 2014

Hi guys,

Using 9.2.1.8

I've been planning a migration towards FreeNAS, from a classical CentOS + SMB server.

As of today, I've set everything up and tested extensively (Shares, snapshots, replications, etc.)

Now it's time to move the files to FreeNAS.

I've been doing RSYNCs so I don't have to wait for a complete transfer.

As I planned it, it's very easy : I just need to shutdown samba services on the old server, do an ultimate RSYNC and then sort out the files.

The last part is my problem : sorting out the files.

You see I've been RSYNCing my files to a directory called /mnt/Data/OLD/

I did it so i can just RSYNC in one place, and I also need to rearrange the structure of the folders for the new Datasets and related CIFS shares.

So today I did my first (FAILED) attempt at migrating.

The problem I had is: I use MV to move the files around, while SSH'ed as ROOT.

When i do so, I get - on almost every line - an error such as :

mv: chmod: <...> Operation not permitted

Now this scared me.

I've done some testing and it looks like some of the files did not move correctly.

Furthermore, they did not actually "move", at least not fully, because the initial folder and files (or most of it in some cases) are still in /mnt/Data/OLD

So most of the time, the files appear at two places - the source and target - but not always fully... some files seem to have been MOVED, so all are on TARGET. Some others stayed in the SOURCE. Finally, some are in both places. I've been trying to find the logic behind this by looking at the permissions, etc... I just can't make it out...

Completely beaten, I lost the battle and started SAMBA on the old server again.

I deleted EVERYTHING, EVERYWHERE and launched another RSYNC to make sure that all files are there, for my next attempt (start fresh).

So I figure this is some kind of permission issue ?

But since I'm ROOT I don't really understand what's going on here...

Maybe I shouldn't use MV at all?

Reading around, I saw it is often recommended to just mount the shares and move files around between them.............. but I don't trust WINDOWS enough to do that.

Data integrity is absolutely essential for me: I want to make sure every single file has been moved, that nothing has been lost and that all files have been moved integrally.

So I would gladly get help on this matter.

I'm very excited to put FreeNAS into production, I'd much like to make another attempt ASAP.

So my questions are:

Do you know what happened? How can I fix this?

What is the best way to do what I want? (get all files from a folder with all kind of files, directories, and permissions... and send them to different datasets, each with CIFS shares and their own permission sets)

anodos · Nov 18, 2014

Did the rsync complete successfully? Part of the problem is that datasets with windows acl type do not typically permit chmod operations because they tend to break nfsv4 permissions. I think an 'mv' between datasets is simply a 'cp' operation followed by an 'rm' operation. It could be the cp has an odd switch in there. What happens if you just 'cp -Rp' a folder?

BlazeStar · Nov 18, 2014

Hi there,

The RSYNC did complete successfully.

I tried a cp -Rp but it would again bother me with permissions.

HOWEVER, a cp -R did work, and that's what I did.

I CP'ed everything, then RM'ed the files after I confirmed they were moved adequately.

Now all my files are in the right place.

However, i'm having a hard time with CIFS permissions...

As discussed in multiple thread, the suggestion seems to be to log in as the admin user, and change the permissions in WINDOWS

I found myself in this unfamiliar interface :
http://cl.ly/image/2Z3q2V1x2a2F

Clicking around I do understand the concept, but I don't understand how to add a GROUP in there...
I mean, when you click EDIT, then ADD, in the dialog box called: "Enter the object names to select" then how do you writ down a GROUP ?

I've been navigating though the useless help dialogs without any luck...

I want to remove all access and add a GROUP then grant the GROUP full control.

anodos · Nov 18, 2014

BlazeStar said:
Clicking around I do understand the concept, but I don't understand how to add a GROUP in there...
I mean, when you click EDIT, then ADD, in the dialog box called: "Enter the object names to select" then how do you writ down a GROUP ?

Hit the "Advanced" button then "Find Now". It will bring up a full list of all users and groups on the FreeNAS server.

BlazeStar · Nov 18, 2014

I wish it did, but it does not :'(

http://cl.ly/image/1t0A1f2V2x3G

anodos · Nov 18, 2014

BlazeStar said:
I wish it did, but it does not :'(

http://cl.ly/image/1t0A1f2V2x3G

Try connecting via hostname. Post your smb4.conf file enclosed in code brackets. /usr/local/etc/smb4.conf

BlazeStar · Nov 18, 2014

Connecting via hostname does exactly the same.

Here's my smb4.conf

Code:

[global]
    server max protocol = SMB3
    interfaces = 127.0.0.1 10.0.3.20 10.99.99.20
    bind interfaces only = yes
    encrypt passwords = yes
    dns proxy = no
    strict locking = no
    oplocks = yes
    deadtime = 15
    max log size = 51200
    max open files = 11070
    load printers = no
    printing = bsd
    printcap name = /dev/null
    disable spoolss = yes
    getwd cache = yes
    guest account = nobody
    map to guest = Bad User
    obey pam restrictions = Yes
    directory name cache size = 0
    kernel change notify = no
    panic action = /usr/local/libexec/samba/samba-backtrace
    server string = NAS
    ea support = yes
    store dos attributes = yes
    hostname lookups = yes
    time server = yes
    acl allow execute always = true
    local master = yes
    idmap config *:backend = tdb
    idmap config *:range = 90000000-100000000
    server role = standalone
    netbios name = NAS
    workgroup = NAS-GROUP
    security = user
    pid directory = /var/run/samba
    smb passwd file = /var/etc/private/smbpasswd
    private dir = /var/etc/private
    create mask = 0666
    directory mask = 0777
    client ntlmv2 auth = yes
    dos charset = CP437
    unix charset = UTF-8
    log level = 1
   

[homes]
    comment = Home Directories
    valid users = %U
    writable = yes
    browseable = no
    path = /mnt/Data/Shares/homes/%U
   

[Tank1]
    path = /mnt/Data/Shares/tank1
    printable = no
    veto files = /.snap/.windows/.zfs/
    writeable = yes
    browseable = yes
    recycle:repository = .recycle/%U
    recycle:keeptree = yes
    recycle:versions = yes
    recycle:touch = yes
    recycle:directory_mode = 0777
    recycle:subdir_mode = 0700
    shadow:snapdir = .zfs/snapshot
    shadow:sort = desc
    shadow:localtime = yes
    shadow:format = auto-%Y%m%d.%H%M-4w
    vfs objects = shadow_copy2 zfsacl streams_xattr aio_pthread
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = yes
    zfsacl:acesort = dontcare

all shares are identical except, of course, for the path.

I'm noticing in the same time that I had changed the HOMES auxilary parameters and it reverted back to what it was originally...

I think it's in relation with a bug in 9.2.1.8, I wonder if upgrading to 9.2.1.9 will fix this...

Anyhow, since I'm not trying to change the HOMES, I don't think it's related...

BlazeStar · Nov 18, 2014

By the way, in OBJECT TYPES, if I CHECK the "Built-in security principals", it will display a list of weird element.

It's the only object that - when selected - actually produces a result, but a result I don't care for ;)

This list is as follow : http://cl.ly/image/0a2c0v2r0g1F

anodos · Nov 18, 2014

BlazeStar said:
By the way, in OBJECT TYPES, if I CHECK the "Built-in security principals", it will display a list of weird element.

It's the only object that - when selected - actually produces a result, but a result I don't care for ;)

This list is as follow : http://cl.ly/image/0a2c0v2r0g1F

Try killing all connections to the server and then modifying permissions. Through cmd.exe "net use * /delete", but my memory is a bit rusty on the specifics of the command.

BlazeStar · Nov 19, 2014

okay so I did the following :

I completely rebooted FreeNAS

I created a new WINDOWS VM (my actual Windows VM had mapped shares)

On the new VM I even ran the command

Code:

net use * /delete

just to make sure.

I proceeded right away to the security tab of a share.

Now to my surprise : the object type USERS does send me the full list of users from my FreeNAS set-up.

But it does not work for the object type GROUPS, which is what I'm looking for :'(

The error message, when I only select GROUPS in the object list, is different :

No items match the current search. Check your search parameters, and try again.

So it appears that the FreeNAS groups are simply invisible to Windows.

How can i fix that ?

anodos · Nov 19, 2014

BlazeStar said:
okay so I did the following :

I completely rebooted FreeNAS

I created a new WINDOWS VM (my actual Windows VM had mapped shares)

On the new VM I even ran the command
Code:
net use * /delete
just to make sure.

I proceeded right away to the security tab of a share.

Now to my surprise : the object type USERS does send me the full list of users from my FreeNAS set-up.

But it does not work for the object type GROUPS, which is what I'm looking for :'(

The error message, when I only select GROUPS in the object list, is different :

So it appears that the FreeNAS groups are simply invisible to Windows.

How can i fix that ?

Do your groups have different names from your users? Are the groups displayed if you type "net groupmap list"?

I can't remember the exact commit / version of FreeNAS, but at some point the samba dev made it so that groups that have names identical to users aren't mapped (as a workaround for some winbind wackiness).

BlazeStar · Nov 19, 2014

anodos said:
Do your groups have different names from your users? Are the groups displayed if you type "net groupmap list"?

I can't remember the exact commit / version of FreeNAS, but at some point the samba dev made it so that groups that have names identical to users aren't mapped (as a workaround for some winbind wackiness).

There's no group that have the same name as users.

All groups have different names than user names.

Concerning "net groupmap list"

In CMD (DOS command line) on my Windows VM, the command did not work.

On FreeNAS, in the console, it returned a list of all the groups I was expecting

Code:

externe (S-1-5-21-23233932-1294756672-3045283348-1014) -> externe
replication (S-1-5-21-1412670398-1815254836-3854788144-1008) -> replication
sysadmin (S-1-5-21-1390711408-50731211-3666900884-1000) -> sysadmin

anodos · Nov 19, 2014

BlazeStar said:
There's no group that have the same name as users.

All groups have different names than user names.

Concerning "net groupmap list"

In CMD (DOS command line) on my Windows VM, the command did not work.

On FreeNAS, in the console, it returned a list of all the groups I was expecting

Code:
externe (S-1-5-21-23233932-1294756672-3045283348-1014) -> externe replication (S-1-5-21-1412670398-1815254836-3854788144-1008) -> replication sysadmin (S-1-5-21-1390711408-50731211-3666900884-1000) -> sysadmin

Try turning off your homes shares.
Review the contents of /var/log/samba4/log.smbd when you are trying to view the groups through a windows client.

BlazeStar · Nov 19, 2014

Turning off homes shares did not do anything.

When I got the list of the users, then try to get the list of the groups, I did not see anything relevant in the

Just to make sure, it's what it displayed in that timeframe

Code:

[2014/11/19 17:43:02.515734,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:02.515810,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:12.328463,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:12.674286,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:12.683421,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:12.683488,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:22.859757,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:22.859851,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:32.675469,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:33.024885,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:33.025988,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:33.026045,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:42.391210,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:42.391293,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:42.399705,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:42.399775,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:43.200328,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:43.200404,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:53.025463,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:53.366572,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:53.367851,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:53.367915,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150

anodos · Nov 19, 2014

BlazeStar said:

Turning off homes shares did not do anything.

When I got the list of the users, then try to get the list of the groups, I did not see anything relevant in the

Just to make sure, it's what it displayed in that timeframe

Code:

[2014/11/19 17:43:02.515734,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:02.515810,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:12.328463,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:12.674286,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:12.683421,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:12.683488,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:22.859757,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:22.859851,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:32.675469,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:33.024885,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:33.025988,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:33.026045,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:42.391210,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:42.391293,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:42.399705,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:42.399775,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:43.200328,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:43.200404,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150
[2014/11/19 17:43:53.025463,  1] ../source3/smbd/server.c:391(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown
[2014/11/19 17:43:53.366572,  1] ../source3/smbd/server.c:438(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2014/11/19 17:43:53.367851,  0] ../source3/lib/util_sock.c:941(matchname)
  matchname: host name/name mismatch: 10.99.99.150 != (NULL)
[2014/11/19 17:43:53.367915,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.99.99.150

Those messages will go away if you disable hostname lookups. Try upgrading to 9.2.1.9.

BlazeStar · Nov 19, 2014

Okay, thanks!

But it still doesn't say why I don't have access to the GROUPS right?

anodos · Nov 19, 2014

BlazeStar said:
Okay, thanks!

But it still doesn't say why I don't have access to the GROUPS right?

There is a bugfix regarding samba SIDs / winbind. It's possible that the bug is causing the problems you are having.
The problem may also be somehow related to your Windows client being a VM and on a different subnet. It's hard to say. Updating to the latest version of FreeNAS will exclude one possibility.

BlazeStar · Nov 19, 2014

anodos said:
There is a bugfix regarding samba SIDs / winbind. It's possible that the bug is causing the problems you are having.
The problem may also be somehow related to your Windows client being a VM and on a different subnet. It's hard to say. Updating to the latest version of FreeNAS will exclude one possibility.

I'm sorry for the misunderstanding, I thought you said that it would fix the hostname lookup problem.

So I just upgraded to 9.2.1.9

Rebooted

Also rebooted my Windows VM.

Sadly... same problem again, I see the USERS but not the groups.

However I have more messages in the console.

Here's an extract :

Code:

Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Nov 19 19:03:14 NAS last message repeated 8 times
Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpC4oRDQ -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Nov 19 19:03:14 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -L
NNov 19 19:03:15 NAS nmbd[3143]: [2014/11/19 19:03:15.922511,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Nov 19 19:03:16 NAS winbindd[3149]: [2014/11/19 19:03:16.050671,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Nov 19 19:03:16 NAS winbindd[3149]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Nov 19 19:03:16 NAS winbindd[3149]: [2014/11/19 19:03:16.102045,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Nov 19 19:03:16 NAS smbd[3146]: [2014/11/19 19:03:16.155941,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Nov 19 19:03:16 NAS smbd[3146]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Nov 19 19:03:17 NAS smbd[3146]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Nov 19 19:03:18 NAS smbd[3146]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Nov 19 19:03:19 NAS smbd[3146]: dnssd_clientstub ConnectToServer: connect() failed Socket:34 Err:-1 Errno:2 No such file or directory
Nov 19 19:03:19 NAS smbd[3319]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.99.99.150 != (NULL)
Nov 19 19:03:19 NAS smbd[3319]: [2014/11/19 19:03:19.171082,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Nov 19 19:03:19 NAS smbd[3319]:   matchname failed on 10.99.99.150
Nov 19 19:03:21 NAS kernel: done.
Nov 19 19:03:21 NAS ntpd[2812]: time reset -0.398084 s
Nov 19 19:03:38 NAS nmbd[3143]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections*****
Nov 19 19:03:38 NAS nmbd[3143]:  
Nov 19 19:03:38 NAS nmbd[3143]:   Samba name server NAS is now a local master browser for workgroup NAS on subnet 10.0.3.20
Nov 19 19:03:38 NAS nmbd[3143]:  
Nov 19 19:03:38 NAS nmbd[3143]:   *****
Nov 19 19:03:38 NAS nmbd[3143]: [2014/11/19 19:03:38.236183,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 19 19:03:38 NAS nmbd[3143]:   *****
Nov 19 19:03:38 NAS nmbd[3143]:  
Nov 19 19:03:38 NAS nmbd[3143]:   Samba name server NAS is now a local master browser for workgroup NAS on subnet 10.99.99.20
Nov 19 19:03:38 NAS nmbd[3143]:  
Nov 19 19:03:38 NAS nmbd[3143]:   *****
Nov 19 19:09:43 NAS smbd[3767]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:09:43 NAS winbindd[3153]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connectionssam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:09:43 NAS winbindd[3153]: [2014/11/19 19:09:43.296647,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:09:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:09:43 NAS winbindd[3153]: [2014/11/19 19:09:43.297033,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:09:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:09:43 NAS winbindd[3153]: [2014/11/19 19:09:43.297334,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:09:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:10:38 NAS smbd[4429]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:10:38 NAS winbindd[3153]: [2014/11/19 19:10:38.641525,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:10:38 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:12:18 NAS winbindd[3153]: [2014/11/19 19:12:18.683721,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:18 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:12:18 NAS winbindd[3153]: [2014/11/19 19:12:18.684074,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:18 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:12:18 NAS winbindd[3153]: [2014/11/19 19:12:18.684379,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:18 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:12:23 NAS winbindd[3153]: [2014/11/19 19:12:23.453827,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:23 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-2888191601-1298625311-3752351526
Nov 19 19:12:23 NAS winbindd[3153]: [2014/11/19 19:12:23.487416,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:23 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:12:23 NAS winbindd[3153]: [2014/11/19 19:12:23.502070,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:12:23 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:13:24 NAS smbd[4550]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:13:24 NAS winbindd[3153]: [2014/11/19 19:13:24.033065,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:13:24 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:41 NAS smbd[4971]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:18:41 NAS smbd[4972]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:18:43 NAS smbd[4974]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:18:43 NAS winbindd[3153]: [2014/11/19 19:18:43.150396,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:43 NAS winbindd[3153]: [2014/11/19 19:18:43.242575,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:43 NAS winbindd[3153]: [2014/11/19 19:18:43.242880,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:43 NAS winbindd[3153]: [2014/11/19 19:18:43.243148,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:43 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:48 NAS winbindd[3153]: [2014/11/19 19:18:48.399623,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:48 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-2888191601-1298625311-3752351526
Nov 19 19:18:48 NAS winbindd[3153]: [2014/11/19 19:18:48.410314,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:48 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:18:48 NAS winbindd[3153]: [2014/11/19 19:18:48.420993,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:18:48 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:19:02 NAS smbd[5014]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsWARNING: The "acl check permissions" option is deprecated
Nov 19 19:19:02 NAS winbindd[3153]: [2014/11/19 19:19:02.558557,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:19:02 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144
Nov 19 19:19:02 NAS winbindd[3153]: [2014/11/19 19:19:02.582654,  0] ../source3/winbindd/winbindd_samr.c:769(sam_rids_to_names)
Nov 19 19:19:02 NAS winbindd[3153]:   sam_rids_to_names: possible deadlock - trying to lookup SID S-1-5-21-1412670398-1815254836-3854788144

Not sure if it will help :S

anodos · Nov 19, 2014

Post your smb4.conf file now that you've upgraded.

BlazeStar · Nov 20, 2014

Here goes :)

Code:

[global]
    server max protocol = SMB3
    interfaces = 127.0.0.1 10.0.3.20 10.99.99.20
    bind interfaces only = yes
    encrypt passwords = yes
    dns proxy = no
    strict locking = no
    oplocks = yes
    deadtime = 15
    max log size = 51200
    max open files = 11070
    load printers = no
    printing = bsd
    printcap name = /dev/null
    disable spoolss = yes
    getwd cache = yes
    guest account = nobody
    map to guest = Bad User
    obey pam restrictions = Yes
    directory name cache size = 0
    kernel change notify = no
    panic action = /usr/local/libexec/samba/samba-backtrace
    server string = NAS
    ea support = yes
    store dos attributes = yes
    hostname lookups = yes
    time server = yes
    acl allow execute always = true
    acl check permissions = true
    dos filemode = yes
    local master = yes
    idmap config *:backend = tdb
    idmap config *:range = 90000000-100000000
    server role = standalone
    netbios name = NAS
    workgroup = NAS
    security = user
    pid directory = /var/run/samba
    smb passwd file = /var/etc/private/smbpasswd
    private dir = /var/etc/private
    create mask = 0666
    directory mask = 0777
    client ntlmv2 auth = yes
    dos charset = CP437
    unix charset = UTF-8
    log level = 1
  

[homes]
    comment = Home Directories
    valid users = %U
    writable = yes
    browseable = no
    path = /mnt/Data/Shares/Employes/%U
    veto files = /.snap/.windows/.zfs/
    vfs objects = zfsacl streams_xattr aio_pthread
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = yes
    zfsacl:acesort = dontcare
  

[Tank-1]
    path = /mnt/Data/Shares/Tank1
    printable = no
    veto files = /.snap/.windows/.zfs/
    writeable = yes
    browseable = yes
    recycle:repository = .recycle/%U
    recycle:keeptree = yes
    recycle:versions = yes
    recycle:touch = yes
    recycle:directory_mode = 0777
    recycle:subdir_mode = 0700
    shadow:snapdir = .zfs/snapshot
    shadow:sort = desc
    shadow:localtime = yes
    shadow:format = auto-%Y%m%d.%H%M-2d
    vfs objects = shadow_copy2 zfsacl streams_xattr aio_pthread
    hide dot files = yes
    guest ok = no
    nfs4:mode = special
    nfs4:acedup = merge
    nfs4:chown = yes
    zfsacl:acesort = dontcare

By the way, is there any other efficient way to set the shares' permissions ?

Such has command lines for the shell ?

Important Announcement for the TrueNAS Community.

Migration to FreeNAS / Moving the file

Patron

Sambassador

Patron

Sambassador

Patron

Sambassador

Patron

Patron

Sambassador

Patron

Sambassador

Patron

Sambassador

Patron

Sambassador

Patron

Sambassador

Patron

Sambassador

Patron

Similar threads