Repository navigation
Conversation
|
please add when a file is unlocked |
tbsbdr
left a comment
There was a problem hiding this comment.
please add the info, when a file is unlocked (eg. after xx. time, close the browser etc?
|
@Svanvith and team: could you please continue here? |
…-files # Conflicts: # docs/user/common-issues/_category_.json # docs/user/common-issues/index.md # i18n/de/docusaurus-plugin-content-docs/current/user/common-issues/_category_.json # i18n/de/docusaurus-plugin-content-docs/current/user/common-issues/index.md # i18n/de/docusaurus-plugin-content-docs/current/user/index.md
|
|
||
| - The file is unlocked as soon as all processing steps have finished. This usually takes only a few seconds. | ||
| - There is no fixed time limit. If a processing step fails, OpenCloud repeats it automatically after an increasing waiting time. | ||
| - If the step still fails after the maximum number of attempts, processing is aborted. In this case, the file stays unavailable until an administrator resumes the processing. |
There was a problem hiding this comment.
That's not what happens. Once the retries run out, postprocessing finishes with PPOutcomeAbort. Reva then rolls back the node and keeps only the uploaded bytes (revertNodeMetadata = true, keepUpload = true in decomposedfs.go on main). So a new file disappears from the folder, and an overwritten file goes back to its previous version. Users won't see a file that is "unavailable". They'll see their upload vanish or their edits missing.
| - The file is unlocked as soon as all processing steps have finished. This usually takes only a few seconds. | ||
| - There is no fixed time limit. If a processing step fails, OpenCloud repeats it automatically after an increasing waiting time. | ||
| - If the step still fails after the maximum number of attempts, processing is aborted. In this case, the file stays unavailable until an administrator resumes the processing. | ||
| - If the virus scan detects malware, the file is deleted or stays blocked, depending on the server configuration. |
There was a problem hiding this comment.
There's also a third option 'continue', in which case the file is just marked as infected but still made available as usual. I suppose we want to list that here too?
| - it is open or being edited in an integrated Office app | ||
| - several users are working on the same Office file at the same time | ||
| - an Office editing session has not ended cleanly yet | ||
| - an upload is still being processed, for example by a virus scan |
There was a problem hiding this comment.
There's actually another case where files get locked. Clients that send WebDAV LOCK (for example desktop Office opening files over WebDAV, or macOS Finder) can lock files too, that's probably worth mentioning here, too.
|
|
||
| ```bash | ||
| opencloud storage-users uploads sessions | ||
| opencloud storage-users uploads sessions --resume |
There was a problem hiding this comment.
--resume won't help here. After the max retries the upload is marked as finished, and resume skips finished uploads, so this needs --restart. Without a filter it also hits every session, including ones still running.
No description provided.