Stale file handle during reading rewritten object with cached metadata about mountpoint-s3 HOT 2 CLOSED

Closing as expected behavior. Feel free to reopen or raise a new issue if you have more questions.

from mountpoint-s3.

This is a similar scenario as in #782, except when trying to get the content, Mountpoint reports that the version that is in the (metadata) cache is stale compared to the one in S3.
I cannot reproduce the successful second attempt, though. When using --cache and --metadata-ttl, Mountpoint will not try to refresh its metadata cache until the TTL expires, except on specific operations, like ls on the containing directory, or when opening the file with the O_DIRECT flag - see details here.

The logs you included do in fact show lines like this:

2024-02-26T09:31:40.493833Z DEBUG readdirplus{req=366 ino=2 fh=28 offset=0}: mountpoint_s3::inode: inode needs to be recreated parent=2 name="file" ino=3

which are likely the result of a ls finding a stale metadata entry and replacing it with a fresh one.

from mountpoint-s3.