Hi, > On Mon, 31 Oct 2022 14:19:24 +0300 Michael Tokarev <m...@tls.msk.ru> wrote: > > Lacking any further information, I'll close this bugreport as fixed in 4.16.
I have just built and tested against 4.16.7 and I'm afraid to say that the reported issue *DOES* still occur. On Tue, 15 Nov 2022 11:03:02 +0300 Michael Tokarev <m...@tls.msk.ru> wrote: > If you think this is incorrect and the issue is still here with current > version > of samba, please feel free to reopen this bug report with any extra > information > which might be helpful to identify the issue. What kind of extra information might be helpful? I can pull diagnostics off my test rig if it helps. Part of me wants to get this issue resolved so that 32-bit systems can meet these use-cases. However, I know from working on the patch for that other bug (https://bugzilla.samba.org/show_bug.cgi?id=13622#c10) that you increase the precision in one part of the code, and sooner or later an issue arises in another. In the end, there's a limit how long it's pragmatic to play bug whack-a-mole like this. Since my previous issue I have upgraded to hardware that supports 64-bit, so I'm now off to validate whether your suggestion of upgrading OS architecture can make this issue magically disappear. Thanks ArtMG
