- 最新
- 最多得票
- 最多評論
Hello,
Please check if the Cache%Dirty metric on the gateway to see if it is above 80% during the copy. Gateway starts throttling the reads and writes to the cache if the metric is above 80%. However, if the large file copy still fails even with the CachePercentDirty metric being less than 80 percent, then your File Gateway might be hitting a client-side session timeout.
For SMB, you can increase this timeout using the PowerShell command below. Running this command sets the timeout to 1800 seconds. The default value is 60 Seconds.
Set-SmbClientConfiguration -SessionTimeout 1800
Also, you can alternatively set the SMB session timeout on the SMB client by updating the registry setting at HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\ LANMANWORKSTATION\PARAMETERS\SESSTIMEOUT.
If the above suggestion did not address the issue, please open a case with AWS support for further investigation.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 4 個月前
Thank you.