New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed upload .part-files remain on file system, no auto remove #26179
Comments
I have also had this problem. Is it a sort of cache so you can resume the upload from where you left off? If so, it should be deleted after 10mins or so. |
In my case the part-files remain (for months now). Maybe file sharing is the significiant item in this issue? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
It's not stale just because no answer came forward. Look at this on nextcloud stable: |
We are seeing this issue too in v25.0.4 |
Me too in 25.0.3. Mostly for one large file (1.3GB) that could not be uploaded several times by the desktop client because of timeouts. The .part files stay for months. |
Steps to reproduce
Expected behaviour
.part files should be automatically removed, if upload has failed.
Actual behaviour
.part file(s) remain on file system. Invisible on nextcloud, only in direct acces to the filesystem
Server configuration
Operating system:
Ubuntu 20.04
Web server:
Apache/2.4.41
Database:
mariadb 10.3.25
PHP version:
7.4.3
Nextcloud version:
20.0.8
Updated from an older Nextcloud/ownCloud or fresh install:
updated
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
local
Are you using encryption: yes/no
no
The text was updated successfully, but these errors were encountered: