Why is a windows 10 pro system issuing a sequence of smb2 commands every 30 seconds or so? SMB2:C CREATE(0x5), Sh(None), QFid, File=NULL@#15679 followed by SMB2:C QUERY INFORMATION(0x10),Class=Query FS Full Size, FID=0xB7CD3148(NULL@#15679) Folowed by SMB2:C CLOSE(0x6),FID=0xB7CD3148(NULL@#15679 Not sure why this sequence starts or stops. But it can run for hours at a time. This is happening with samba 4.3.11. It does not happen with samba 4.0.0 RAC
On Sun, 15 Jul 2018 23:47:37 -0400 rac8006 via samba <samba at lists.samba.org> wrote:> > Why is a windows 10 pro system issuing a sequence of smb2 commands > every 30 seconds or so?Go on, I give in, why is YOUR windows 10 pro system issuing them ?> > SMB2:C CREATE(0x5), Sh(None), QFid, File=NULL@#15679 followed by > > SMB2:C QUERY INFORMATION(0x10),Class=Query FS Full Size, > FID=0xB7CD3148(NULL@#15679) Folowed by > > SMB2:C CLOSE(0x6),FID=0xB7CD3148(NULL@#15679 > Not sure why this sequence starts or stops. But it can run for hours > at a time. This is happening with samba 4.3.11. It does not happen > with samba 4.0.0Are you sure it isn't happening with 4.0.0 or was it just not reported way back then. Both 4.0.0 and 4.3.11 are EOL as far as Samba is concerned, have you tried a supported version. If your Win10 machine is contacting Samba every 30 seconds, this is nothing to do with Samba, it is coming from the Windows client. You need to find out what on the client is sending the commands. Rowland
On Mon, 16 Jul 2018 10:21:21 -0400 rac8006 at aol.com wrote:> > > If it is only a windows problem. Wouldn't windows try to do this > sequence to all shared devices? This only happens to the devices > running 4.3.11. Each device has a Public folder mapped to a windows > drive letter. There are 5 samba shares > > mapped on the windows PC. Two running 4.3.11 and the rest running an > older version. The smbd log show that it is doing something with > Public/. directory. The strace shows > geteuid32() = 0 > getegid32() = 0 setgroups32(3, [1000, > 501, 2000]) = 0 setresgid32(-1, 1000, -1) = 0 > getegid32() = 1000 > setresuid32(1002, 1002, -1) = 0 > geteuid32() = 1002 > stat64(".", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 > stat64(".", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 > getxattr(".", "system.posix_acl_access", 0xbe92eee0, 132) = -1 > ENODATA (No data available) stat64(".", {st_mode=S_IFDIR|0777, > st_size=4096, ...}) = 0 getxattr(".", "system.posix_acl_default", > 0xbe92eee0, 132) = -1 ENODATA (No data available) stat64(".", > {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 > > > I'm not well versed on samba and smb protocol. I'm not looking for a > fix to 4.3.11. I'm trying to understand what is happening. > All of the mapped shares are working. >No, it doesn't mean it is only happening with 4.3.11, it means it is only being reported on 4.3.11, it is very probably happening on your 4.0.0 machine, it just isn't getting reported. What ever is happening, it is originating from your Windows 10 machine, neither the 4.0.0 or any 4.3.11 Samba machine is starting it, it is all coming from the Windows 10 machine, Samba is just reacting to it. If something does need fixing on your Samba machine (and I am not saying anything does need fixing), you have less than no chance of getting it fixed. As far as Samba is concerned, the only supported Samba versions are 4.6.x, 4.7.x and 4.8.x and, in a matter weeks, 4.6.x will go EOL when 4.9.0 is released. You need to find what is connecting to Samba from the Windows 10 PC and fix this, your problem seems to be a Windows problem and not a Samba problem. Rowland
On Mon, 16 Jul 2018 10:53:10 -0400 rac8006 at aol.com wrote:> > If it was happening on 4.0.0 I would know. The reason this problem > is detected is that the disk will not sleep while this is happening. > The windows PC's are logged in with user rac. The uid 1002 is for > rac. I think there is something wrong with the smb.conf file. I > don't use the rac folder on network device. But there is an entry > for an rac share. The smb.conf information is generated by the web > interface used to configure the network device. I think there is a > problem with the rac entry. rac is not a valid user of rac share. > I'm going to change the smb.conf file and see it that is the problem. >The problem is coming from Windows 10 , but 4.0.0 isn't reacting, so nothing is written to the disk, so it goes to sleep. I repeat, you have a Windows 10 problem, something on the Windows 10 is spamming the Samba machines, you need to find what this is. Samba is doing nothing other than reacting to this 'spamming'. Rowland