This was exactly what I needed to solve my issue. That means that file and directory changes are immediately visible for the client. ![]() This configuration change disables the client side directory content cache. My google-fu helped me to find the TechNet article SMB2 Client Redirector Caches Explained that explains the Windows SMB2 Cache and it’s configuration options. Linux and OS X clients were not affected by this issue and so it was clear that this had to be a client side caching problem. ![]() Even manually refreshing the parent folder did not help. Sometimes it took several minutes for the files and directories to show up. ![]() Currently I’m busy building several automated workflows that run on our flow:rage Video Storage System and that move files and directories from A to B while processing them in some way.ĭuring qualifying this workflows for production we discovered that moved items were not immediately visible for Windows clients connected using SMB.
0 Comments
Leave a Reply. |