You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sandboxfs currently does not track ctimes for the nodes it manages. Instead, it relies on the ctimes returned by the underlying file systems and propagates those to the caller.
This has unfortunate consequences: because we don't track ctimes, we cannot synthesize what the attributes of a file should be e.g. immediately after creation, which means we end up issuing extra stat calls in cases where we shouldn't.
So: track ctimes (and possibly also creation times) and avoid these unnecessary operations.
The text was updated successfully, but these errors were encountered:
jmmv
added a commit
to jmmv/sandboxfs
that referenced
this issue
Oct 28, 2018
sandboxfs currently does not track ctimes for the nodes it manages. Instead, it relies on the ctimes returned by the underlying file systems and propagates those to the caller.
This has unfortunate consequences: because we don't track ctimes, we cannot synthesize what the attributes of a file should be e.g. immediately after creation, which means we end up issuing extra stat calls in cases where we shouldn't.
So: track ctimes (and possibly also creation times) and avoid these unnecessary operations.
The text was updated successfully, but these errors were encountered: