Use "part" folder for huge file operations

[PVince81]

When deleting a huge folder with subfolders, it can take a long time to move it to trash (especially if from external storage).

One idea would be to first rename the folder "test" to "test.part" to make it invisible to regular file operations. At this point neither web UI nor sync client will see it, so it will appear as deleted, while the "test.part" folder is still being moved to trash.

Such idea could in some way also be applied to cross-storage renames (the ones where copy is not avoidable). The target folder could first be written as "target.part" on the target storage, and once all files are there, rename it to the final one.

What do you think ? @schiesbn @icewind1991 @karlitschek @DeepDiver1975

[DeepDiver1975]

interesting approach - this would also allow us to perform the real operation async.

[PVince81]

• use part folder when renaming folders
• use part file for rename/copy/streamcopy

I'm setting this to 8.2 so we keep an eye on it.
If a PHP timeout would happen during a streamCopy it could result in partially written / broken files.

[PVince81]

Moving this discussion to 9.0

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)