Smb errors!

macafee · Post by **macafee** » 25 Dec 2014 13:35

Today, I fresh install the nas4free 9.3.0.2 - Nayla (revision 1213). Everything is good but smb that I meet the strang problem.
I found many errors in the log.

Code: Select all

nmbd[1896]: [2014/12/25 20:33:15.386817, 0] ../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Dec 25 20:29:15 	backup 	smbd[2312]: unknown tag type 64
Dec 25 20:29:15 	backup 	smbd[2312]: [2014/12/25 20:29:15.693994, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Dec 25 20:29:11 	backup 	smbd[2312]: unknown tag type 64
Dec 25 20:29:11 	backup 	smbd[2312]: [2014/12/25 20:29:11.636678, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Dec 25 20:29:11 	backup 	smbd[2312]: unknown tag type 64
Dec 25 20:29:11 	backup 	smbd[2312]: [2014/12/25 20:29:11.397790, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)

How to resolve this problem?

lukinomt · Post by **lukinomt** » 28 Dec 2014 12:18

Hello, looks you are not only one with the problems

(+1)

maulbongo · Post by **maulbongo** » 29 Dec 2014 11:53

Since upgrading to 9.3.0.2 I get loads of errors with Samba

Code: Select all

Dec 29 11:43:38	ewnas01	smbd[10882]: STATUS=daemon 'smbd' finished starting up and ready to serve connections===============================================================
Dec 29 11:43:38	ewnas01	smbd[10882]: [2014/12/29 11:43:38.010584, 0] ../lib/util/fault.c:73(fault_report)
Dec 29 11:43:38	ewnas01	smbd[10882]: INTERNAL ERROR: Signal 11 in pid 10882 (4.1.14)
Dec 29 11:43:38	ewnas01	smbd[10882]: Please read the Trouble-Shooting section of the Samba HOWTO
Dec 29 11:43:38	ewnas01	smbd[10882]: [2014/12/29 11:43:38.010650, 0] ../lib/util/fault.c:75(fault_report)
Dec 29 11:43:38	ewnas01	smbd[10882]: ===============================================================
Dec 29 11:43:38	ewnas01	smbd[10882]: [2014/12/29 11:43:38.010678, 0] ../source3/lib/util.c:785(smb_panic_s3)
Dec 29 11:43:38	ewnas01	smbd[10882]: PANIC (pid 10882): internal error
Dec 29 11:43:38	ewnas01	smbd[10882]: [2014/12/29 11:43:38.010923, 0] ../source3/lib/util.c:896(log_stack_trace)
Dec 29 11:43:38	ewnas01	smbd[10882]: BACKTRACE: 5 stack frames:
Dec 29 11:43:38	ewnas01	smbd[10882]: #0 0x802ca609c <smb_panic_s3+108> at /usr/local/lib/libsmbconf.so.0
Dec 29 11:43:38	ewnas01	smbd[10882]: #1 0x801469bc5 <smb_panic+37> at /usr/local/lib/libsamba-util.so.0
Dec 29 11:43:38	ewnas01	smbd[10882]: #2 0x8014698d7 <fault_setup_disable+407> at /usr/local/lib/libsamba-util.so.0
Dec 29 11:43:38	ewnas01	smbd[10882]: #3 0x8014698f3 <fault_setup_disable+435> at /usr/local/lib/libsamba-util.so.0
Dec 29 11:43:38	ewnas01	smbd[10882]: #4 0x804506236 <pthread_sigmask+918> at /lib/libthr.so.3
Dec 29 11:43:38	ewnas01	smbd[10882]: [2014/12/29 11:43:38.011097, 0] ../source3/lib/dumpcore.c:312(dump_core)
Dec 29 11:43:38	ewnas01	smbd[10882]: unable to change to %N.core
Dec 29 11:43:38	ewnas01	smbd[10882]: refusing to dump core
Dec 29 11:43:38	ewnas01	smbd[10804]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsScheduled cleanup of brl and lock database after unclean shutdown

Which is really annoying, because it slows down a lot and often shares and files are not accessable anymore.

I testet nearly every setting for samba, but no luck.
Unfortunately I was to fast and after Upgrading, I also upgraded the zfs features, so Downgrading is not possible anymore, because 9.2 does not recognize the pool anymore.
Is there a possibility to revert back to Samba 3.6, because this worked like a charm, or could you dao and zoon provide a quick fix build of 9.3 which includes samba 3.6 instead of 4?

Onichan · Post by **Onichan** » 30 Dec 2014 03:04

I was getting frequent crashes as well and after trying a bunch of different auxiliary parameters I might have it working. So far after a bunch of transfer tests and running for a day I haven't gotten any more crashes, but still get the tag errors.

What seems to have stopped the crashes is:
Max Protocol SMB2
disable sendfile and disable AIO

Then you must reboot all clients!

Also during the testing I added

Code: Select all

kernel change notify = no

to the auxiliary parameters, but I'm not sure if that was required.

maulbongo · Post by **maulbongo** » 30 Dec 2014 09:37

Thanks for the tip I'm testing this at the moment and report back.

maulbongo · Post by **maulbongo** » 02 Jan 2015 15:37

The "kernel change notify = no" did the job.

Max Protocol put to smb3 use sendfile is deactivatet, because this causes trouble (with smb2 this can't be activated) AIO is enabled.
So all works like a charme again, as it was before, thanks.

Post by **daoyama** » 02 Jan 2015 19:49

maulbongo wrote:Max Protocol put to smb3 use sendfile is deactivatet, because this causes trouble (with smb2 this can't be activated)

It's a bug! I will fix.

maulbongo · Post by **maulbongo** » 02 Jan 2015 20:24

Hi dao,

whats the bug, that it's not working with smb2 or causing trouble with smb3?
Thanks anyway for your good and fast work.

maulbongo · Post by **maulbongo** » 02 Jan 2015 20:33

Ah, already read the commit

Onichan · Post by **Onichan** » 02 Jan 2015 23:20

maulbongo wrote:The "kernel change notify = no" did the job.

Max Protocol put to smb3 use sendfile is deactivatet, because this causes trouble (with smb2 this can't be activated) AIO is enabled.
So all works like a charme again, as it was before, thanks.

Thanks, I figured all of it wasn't required. I was just trying to get it working right then and was planning to eventually go back and individually test them all.

Post by **MikeMac** » 09 Jan 2015 23:50

I could confirm. Log of my NAS (build 1213) is full of

Code: Select all

Jan 10 01:40:02 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:02 	smbd[3966]: 	[2015/01/10 01:40:02.056996, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Jan 10 01:40:01 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:01 	smbd[3966]: 	[2015/01/10 01:40:01.682267, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Jan 10 01:40:01 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:01 	smbd[3966]: 	[2015/01/10 01:40:01.364452, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)

during copy form win7 machine
SMB2, senfile off, AIO on
By the way, changing of SMB2 to SMB3 and switching AIO off does not changed mentioned log entries - messages continue to appear.

I had tried to reboot both NAS and only Windows machine in the my neywork after last partemeters change to SMB2 ans AIO on - no influence.

Concerning "kernel change notify = no"
I am afraid, this only hides the problem, not solved.

crutch · Post by **crutch** » 09 Jan 2015 23:58

macafee wrote:Today, I fresh install the nas4free 9.3.0.2 - Nayla (revision 1213). Everything is good but smb that I meet the strang problem.
I found many errors in the log.
How to resolve this problem?

Hello, macafee.
Could you please check the ZFS ACL (This will provide ZFS ACL support) checkbox in the properties of your share and try again?
In my installation I don`t use an ACL functionality, but 'unknown tag type 64' messages have gone after the option specified has been enabled.

Onichan · Post by **Onichan** » 10 Jan 2015 03:29

MikeMac wrote:I could confirm. Log of my NAS (build 1213) is full of
Code: Select all
Jan 10 01:40:02 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:02 	smbd[3966]: 	[2015/01/10 01:40:02.056996, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Jan 10 01:40:01 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:01 	smbd[3966]: 	[2015/01/10 01:40:01.682267, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
Jan 10 01:40:01 	smbd[3966]: 	unknown tag type 64
Jan 10 01:40:01 	smbd[3966]: 	[2015/01/10 01:40:01.364452, 0] ../source3/modules/vfs_posixacl.c:171(smb_ace_to_internal)
during copy form win7 machine
SMB2, senfile off, AIO on
By the way, changing of SMB2 to SMB3 and switching AIO off does not changed mentioned log entries - messages continue to appear.

I had tried to reboot both NAS and only Windows machine in the my neywork after last partemeters change to SMB2 ans AIO on - no influence.

Concerning "kernel change notify = no"
I am afraid, this only hides the problem, not solved.

MikeMac, the kernel change notify = no and sendfile=off was only to fix the crashes, not to fix the unknown tag. While the unknown tag is annoying, it doesn't appear to effect anything, while the frequent crashes were causing a lot of problems.

Post by **MikeMac** » 10 Jan 2015 13:04

Onichan wrote: While the unknown tag is annoying, it doesn't appear to effect anything

I have not seen crashes yet, thank you for advice. But I am glad to share simple solution against unknown tag 64 messages, found by reader of my Russian blog.

Just check option ZFS ACL (This will provide ZFS ACL support) at smb share control dialog. This option is unchecked by default.

I had this done and and do not see annoyng messages anymore

smish · Post by **smish** » 15 Jan 2015 17:15

Onichan wrote:
Also during the testing I added
Code: Select all
kernel change notify = no
to the auxiliary parameters, but I'm not sure if that was required.

Just reporting this worked for me as well. Thank you good sir!

stayhard · Post by **stayhard** » 05 Feb 2015 21:48

Im getting this in my log:

smbd[59754]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to fetch record!
nmbd[2297]: [2015/02/05 22:05:18.154442, 0] ../source3/nmbd/nmbd_incomingrequests.c:118(process_name_release_request)
nmbd[2297]: process_name_release_request: Attempt to release name WORKGROUP<1d> from IP 192.168.0.106 on subnet 192.168.0.107 being rejected as it is one of our names.

What is the problem? The server is working perfect, or is it just me who do not notice it?

EDIT!!
I had my windows 7 machine connected to a homegroup, leaved that and connected to a workgroup instead. Not a single post in the log now

morestress · Post by **morestress** » 17 Mar 2015 07:31

maulbongo wrote:The "kernel change notify = no" did the job.

Max Protocol put to smb3 use sendfile is deactivatet, because this causes trouble (with smb2 this can't be activated) AIO is enabled.
So all works like a charme again, as it was before, thanks.

Hi,
I'm fairly new to Nas4Free.
Can you please tell me how to do this "kernel change notify = no"?
I didn't see anything in the GUI.
Thanks

maulbongo · Post by **maulbongo** » 17 Mar 2015 07:36

Hi,

you can add these within "services/cifs/smb/settings"

At the Bottom there is an option "Auxiliary parameters"

infinion · Post by **infinion** » 03 Feb 2016 13:54

crutch wrote:
macafee wrote:Today, I fresh install the nas4free 9.3.0.2 - Nayla (revision 1213). Everything is good but smb that I meet the strang problem.
I found many errors in the log.
How to resolve this problem?
Hello, macafee.
Could you please check the ZFS ACL (This will provide ZFS ACL support) checkbox in the properties of your share and try again?
In my installation I don`t use an ACL functionality, but 'unknown tag type 64' messages have gone after the option specified has been enabled.

Just upgraded from 972 Shigawire Full to 2268 Jesper Embedded and this fixed the type 64 log entries for me. Thanks!
Added, this required save & restart on the smdb service and a reboot of the clients.

XigmaNAS

Smb errors!

Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!

Re: Smb errors!