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
I don't have evidence for it, but I have a hunch that this happened because of a concurrent write by multiple independent processes. This is outlined as not supported, and I thought I was careful enough that it would not happen. But the other day I observed that the onedrive client on a machine on which no one was doing any active work, started suddenly uploading encrypted chunks after having been downloading them as I was editing on a different machine. I'm puzzled by this. Can cryfs be the cause of the writes?
EDIT: I just realized that the language that forbids concurrent access doesn't talk about writes specifically, but concurrent access in general. So probably it means concurrent mounting is always bad even if the user is careful enough not to write?
EDIT2: For clarity: I have two machines, each has a directory, and the two directories are synchronized via onedrive client. The directory on each machine is backing cryfs, which is perpetually mounted on that machine.
Input/output error when I run
ls
on one of the directories.Expected Behavior
No errors.
Actual Behavior
Stack trace:
Steps to Reproduce the Problem
I don't know.
Specifications
The text was updated successfully, but these errors were encountered: