- 最新
- 最多得票
- 最多評論
Hi Yaniv,
Stale file handles can occur when the file gateway is rebooted and there are clients with open files from the gateway NFS share. File handles for these open files can get invalid on the server side when one of the clients removes an open file. You can use file gateway audit logs to review the client activity. You may resolve this error by un-mounting/re-mounting the NFS share on the client, or rebooting the client. Thank you - Surya
Hi
and what i'm suppose to configure in the logs ? Also, remounting will not work if there is a problem in the storage gateway. it's a black box.
Hi, audit logs on the NFS file share would give insight into which client deleted the file when it it is being used by a different client at the same time.
To prevent running into the issue, application/client should coordinate and delete a file when it is not in use by any other client. If remounting doesn't work, rebooting the NFS client usually resolves this error and clears the stale file error reported by the client.
相關內容
- 已提問 1 年前
- 已提問 6 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 10 個月前
- AWS 官方已更新 2 年前