My name is Brian and I am with the Storage Gateway team.
If this was a timeout for the session in Windows I'd expect more of a semaphore timeout error. Since you mentioned that this is writing for a few minutes then errors out I would rule out Active Directory permissions.
With the behavior described it would sound more like the gateway is denying the write because the cache is full which the gateway would return as an I/O error but some applications may show as permissions.
Can you check the metrics/monitoring tab in the Storage Gateway web console and see what the Cache Percent Dirty metric is at the times you get that error? If it's 90% or greater then it would mean you are writing to the gateway faster than it can upload.
If that is the case you would need to add more cache disk(s) to the gateway (do not modify or remove existing cache disks only add new ones) or increase the amount of bandwidth available to the gateway for uploads.
Thank you Brian, I think you are right. The problem is the cache as I have some dirty cache peeks during those copies.
Storage Gateway can't mount File Shareasked 5 months ago
Copy or move fileasked 21 hours ago
SMB File Share On Storage Gateway With Windows Permissionasked 7 months ago
How do I upload a checkpoint file to my Github repoasked 2 years ago
SMB File Gateway Joined to Domain - PermissionsAccepted Answerasked 3 years ago
tagging to AWS FSx windows file systemAccepted Answerasked 7 months ago
"You need permissions to perform this action" copying file to storage gat.asked 3 years ago
S3 version disappeared if updating file in the Storage Gateway file share in ONE minuteAccepted Answerasked 6 months ago
AWS Storage gateway and read only shareAccepted Answerasked 8 months ago
Storage Gatweay (file) for migration?asked 3 years ago