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
users have large folders with a few thousands files
they try to delete folders in the client and it takes "forever"
they receive timeout after waiting "forever"
what happens after that:
files are deleted on the desktop client
files are NOT deleted in the web browser
-> files are still visible in the web browser
problems which occur after that:
files_trashbin folder is getting bigger and bigger because SAME files are being deleted over and over again but they are not removed from their original folder
users have over a million files in then files_trashbin folder
-> effect: trashbin cannot be used anymore
they are not able to remove files from trashbin folder anymore
-> every click on trashbin icon (in web browser) takes forever
now, for these users, deleting even a single file causes same
problem again:
-> file is basically never delete from folder
-> file is visible in the folder
-> file IS in trashbin TOO
-> it comes to timeout (see client log below)
as you can see, their files_trashbin (878G) folder is big and it is
getting bigger and bigger because now deleting even a single file is not
possible and there are hundreds of copies of the same file in the
trashbin but the file is still not removed from the original folder.
one example of current behavior of this problem:
user uploaded file workflow_a0_sav.indd
user deleted this file
deletion takes forever
file is still visible in the original folder
there are currently 112 same copies of this deleted file in files_trashbin/files:
$ ls -l files_trashbin/files/workflow_a0_sav.indd* | more
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424038944
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424039258
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080319
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080661
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080998
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424081337
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424081647
$ ls -l files_trashbin/files/workflow_a0_sav.indd* | wc -l
112
WHAT CAN WE DO?
can we delete all files (from the affected users) from files_trashbin on the command line:
$ cd files_trashbin/files
$ rm -rf *
we did that once on v6.0.3 and user was not able to open trashbin anymore.
if this is not a recommended/possible way to do this, what should we do?
Log
19:57 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
19:47 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
19:36 Poster/e-Infra/~workflow_a0~f-5cl).idlk SERVERNAME Could not read status line: connection timed out
19:31 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: Connection reset by peer
19:21 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
19:10 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
19:00 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:49 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:38 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:28 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:17 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:12 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:06 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
18:00 Poster/e-Infra/workflow_a0_sav.indd SERVERNAME Could not read status line: connection timed out
What users do:
what happens after that:
-> files are still visible in the web browser
problems which occur after that:
-> effect: trashbin cannot be used anymore
-> every click on trashbin icon (in web browser) takes forever
problem again:
-> file is basically never delete from folder
-> file is visible in the folder
-> file IS in trashbin TOO
-> it comes to timeout (see client log below)
this is one of these accounts:
cloud@server:~/html/data/[email protected] $ du -sh *
331M cache
6.4G files
878G files_trashbin
494M files_versions
4.1M gallery
238M thumbnails
as you can see, their files_trashbin (878G) folder is big and it is
getting bigger and bigger because now deleting even a single file is not
possible and there are hundreds of copies of the same file in the
trashbin but the file is still not removed from the original folder.
one example of current behavior of this problem:
$ ls -l files_trashbin/files/workflow_a0_sav.indd* | more
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424038944
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424039258
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080319
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080661
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424080998
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424081337
-rw-r--r-- 1 cloud cloud 483328 Feb 14 19:33 workflow_a0_sav.indd.d1424081647
$ ls -l files_trashbin/files/workflow_a0_sav.indd* | wc -l
112
WHAT CAN WE DO?
we did that once on v6.0.3 and user was not able to open trashbin anymore.
Log
Client Version
1.7.0 (build 1385)
Server Version
7.0.3.4
@MorrisJobke
00002612
The text was updated successfully, but these errors were encountered: