I have done some more poking around and it appears that as the Eclipse IDE is closing it is getting stuck in a loop. I can see SMB transactions on the network using Wireshark and also repeated file accesses on the server using inotifywait. I?m not sure whether I am interpreting the data I have collected correctly but it looks as though Eclipse is missing a notification that file(s) have been successfully closed and so is repeating the request. Does that make any sense? -Andy.
On Tue, 2022-06-07 at 09:49 +0000, Andy Pont via samba wrote:> I have done some more poking around and it appears that as the > Eclipse > IDE is closing it is getting stuck in a loop. I can see SMB > transactions on the network using Wireshark and also repeated file > accesses on the server using inotifywait. > > I?m not sure whether I am interpreting the data I have collected > correctly but it looks as though Eclipse is missing a notification > that > file(s) have been successfully closed and so is repeating the > request. > > Does that make any sense? > > -Andy.Possibly, there was a discussion on the samba-technical mailing list about 'SMB2_LOGOFF', you can find it here: https://lists.samba.org/archive/samba-technical/2022-March/137186.html I wonder if your Eclipse IDE is suffering from the same problem. Rowland
On Tue, Jun 07, 2022 at 09:49:17AM +0000, Andy Pont via samba wrote:>I have done some more poking around and it appears that as the Eclipse >IDE is closing it is getting stuck in a loop. I can see SMB >transactions on the network using Wireshark and also repeated file >accesses on the server using inotifywait. > >I?m not sure whether I am interpreting the data I have collected >correctly but it looks as though Eclipse is missing a notification that >file(s) have been successfully closed and so is repeating the request.What version of Samba is this ? This smells to me like the duplicate fileid problem we fixed in the latest 4.15, 4.16.