Changes made directly in S3 not reflected in SMB share after RefreshCache update

Hi

Here are some of the issues I can assume,

• Targeted Refresh: Did you use the RefreshCache command on the specific file share where you expect the new prefix? If you have multiple shares, each needs a separate refresh.
• Time Consistency
• Some SMB clients might cache directory listings. Try clearing the cache on your SMB client application

Gateway file share issues: https://repost.aws/knowledge-center/storage-gateway-s3-changes-not-showing

This resource also provides insights into refreshing the cache: https://repost.aws/knowledge-center/storage-gateway-s3-changes-not-showing

Hello.

Does this mean that you updated the cache using the steps in the document below?
https://repost.aws/knowledge-center/storage-gateway-s3-changes-not-showing
https://docs.aws.amazon.com/filegateway/latest/files3/troubleshooting-file-share-issues.html#s3-changes-issue

It may be taking some time to update the cache, so it may be a good idea to wait a while.
https://repost.aws/knowledge-center/storage-gateway-refreshcache-latency