- Fix occasional “permission denied” error when syncing a library
- [Win] Remove explorer shortcut when uninstall SeaDrive or change cache folder location
3 Likes
SeaDrive/Shared with all
not Available to show. （I’m the admin, and I create this library to share with all)
The normal users can see this library with seadrive.
Is anyone else experiencing slow transfer rates with the SeaDrive client?
Task-Manger shows max. 100 Mbit on the 1 Gbit line and high CPU usage for seadrive.exe.
The 1 Gbit line is saturated downloading the same files from the same server using Rclone.
I have three more issues with SeaDrive 2.0.x. The last one is critical.
1.) Locked files can be deleted in SeaDrive, but deletion is not synced back to the server. As a result, there is a discrepency between the files shown in SeaDrive and Seahub.
Steps to reproduce:
a.) Open DOCX file in Seahub -> file is shown as locked in Seahub and SeaDrive
b.) Delete file in SeaDrive -> file is deleted locally, but not on the server
c.) Unlocking the file on the server -> File is shown unlocked in SeaHub and remains gone in in SeaDrive; refreshing SeaDrive does not help; a reboot does
2.) Situation: I am member of two departments. One department membership gives me read-write access to a library, the other membership gives me read-only access to the same library. In SeaDrive, the library is treated as if I have read-only access which keeps me from uploading modified files.
3.) When moving files from one folder to another within one library, some files are corrupted in the target folder and cannot be opened any more. On the server, the moved files have disappeared and cannot be found in neither the source nor the target folder.
This video demonstrates the problem. When watching it, focus on the files with the sync pending logo. It is them that get corrupted in the moving process.
Important note 1: All files were fine before they got moved.
Important note 2: I have NOT encountered the same problem when copy-pasting files.
Important note 3: I have NOT encountered the same problems when cut-pasting files between libraries.
Not shown in the video is another problem (and not reproducible reliably): When moving all files from one folder to another folder, the empty source folder cannot be deleted. Not always, but sometimes.
Will the old method of having a dedicated drive eventually be removed completely? Of course it makes sense to use the Cloud Files API but I always found it kind of nice to have that drive as well.
@mydoom The drive is not kept in 2.0 version. We cannot keep both mechanism. They cannot work together.
@Jonathan: Are you sure about this? As a workaround I now use “subst y: d:\Seadrive\arnova” to bring back the driveletter. As a worstcase option you could use that for SeaDrive but I assume it should also be possible with native Windows API, right?
Could you please make a statement?
If this is not only an edge case, it is a really critical bug.
@Jonathan @daniel.pan
This is caused by network timeout. It’ll be fixed in the next version.
And when the new version is available, please?
Hi @Jonathan
I still have “permission denied” errors, but only for read-only Libraries
It is not an issue but users mayu misunderstand that
see seadrive.log
[09/02/20 09:13:44] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/233a4681-bf6a-47ca-b19d-3ebf6a1003a4/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:13:44] Upload permission denied for repo 233a4681 on server https://seafile.domaine.fr.
[09/02/20 09:13:44] Transfer repo '233a4681': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:13:44] Repo 'CC - SUPPORT INFORMATIQUE - WIKI INTERNE' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
[09/02/20 09:13:56] Repo 'GED - Documentation du projet' sync state transition from 'synchronized' to 'uploading'.
[09/02/20 09:13:56] Upload with HTTP sync protocol version 2.
[09/02/20 09:13:56] Transfer repo '6641a7e8': ('normal', 'init') --> ('normal', 'check')
[09/02/20 09:13:56] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/6641a7e8-ec3a-4caa-aec2-d3d512e8bf49/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:13:56] Upload permission denied for repo 6641a7e8 on server https://seafile.domaine.fr.
[09/02/20 09:13:56] Transfer repo '6641a7e8': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:13:56] Repo 'GED - Documentation du projet' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
[09/02/20 09:14:14] Repo 'CC - SUPPORT INFORMATIQUE - WIKI INTERNE' sync state transition from 'synchronized' to 'uploading'.
[09/02/20 09:14:14] Upload with HTTP sync protocol version 2.
[09/02/20 09:14:14] Transfer repo '233a4681': ('normal', 'init') --> ('normal', 'check')
[09/02/20 09:14:14] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/233a4681-bf6a-47ca-b19d-3ebf6a1003a4/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:14:14] Upload permission denied for repo 233a4681 on server https://seafile.domaine.fr.
[09/02/20 09:14:14] Transfer repo '233a4681': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:14:14] Repo 'CC - SUPPORT INFORMATIQUE - WIKI INTERNE' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
[09/02/20 09:14:27] Repo 'GED - Documentation du projet' sync state transition from 'synchronized' to 'uploading'.
[09/02/20 09:14:27] Upload with HTTP sync protocol version 2.
[09/02/20 09:14:27] Transfer repo '6641a7e8': ('normal', 'init') --> ('normal', 'check')
[09/02/20 09:14:27] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/6641a7e8-ec3a-4caa-aec2-d3d512e8bf49/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:14:27] Upload permission denied for repo 6641a7e8 on server https://seafile.domaine.fr.
[09/02/20 09:14:27] Transfer repo '6641a7e8': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:14:27] Repo 'GED - Documentation du projet' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
[09/02/20 09:14:30] Repo 'CC - Partenariat - Interfaces' sync state transition from 'synchronized' to 'uploading'.
[09/02/20 09:14:30] Upload with HTTP sync protocol version 2.
[09/02/20 09:14:30] Transfer repo '31574e7d': ('normal', 'init') --> ('normal', 'check')
[09/02/20 09:14:30] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/31574e7d-db5a-426b-877c-4afdd9085360/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:14:30] Upload permission denied for repo 31574e7d on server https://seafile.domaine.fr.
[09/02/20 09:14:30] Transfer repo '31574e7d': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:14:30] Repo 'CC - Partenariat - Interfaces' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
[09/02/20 09:14:45] Repo 'CC - SUPPORT INFORMATIQUE - WIKI INTERNE' sync state transition from 'synchronized' to 'uploading'.
[09/02/20 09:14:45] Upload with HTTP sync protocol version 2.
[09/02/20 09:14:45] Transfer repo '233a4681': ('normal', 'init') --> ('normal', 'check')
[09/02/20 09:14:46] Bad response code for GET https://seafile.domaine.fr/seafhttp/repo/233a4681-bf6a-47ca-b19d-3ebf6a1003a4/permission-check/?op=upload&client_id=1a7a549017d45082fba8486ad7476f7784bcbdb2&client_name=NUM14: 403.
[09/02/20 09:14:46] Upload permission denied for repo 233a4681 on server https://seafile.domaine.fr.
[09/02/20 09:14:46] Transfer repo '233a4681': ('normal', 'check') --> ('error', 'finished')
[09/02/20 09:14:46] Repo 'CC - SUPPORT INFORMATIQUE - WIKI INTERNE' sync state transition from uploading to 'error': 'Do not have write permission to the library'.
you can uninstall seadrive,
delete seadrive related folders, configuration files.
then reinstall,
re login with user account,
this will fix the problem.
Is there still no plans in regards to allowing a flat folder structure in SeaDrive like the old versions? … or atleast less “Shared with…” folders?
What do mean by “… like in the old versions?” SeaDrive 1 and SeaDrive 2 have the same folder structure characterized by 4 category folders (My libs, shared with me, shared with groups, shared with all).
I am all for more flexibility as to whether all these folders are displayed or if they are used at all. But this would be a totally new feature.
By old I meant pre-0.9.0.
Ah, I don’t even remember those!
Is there a release date for a SeaDrive version in which the network timeout problem (see above, my 3.) will be removed? I just had a user on the phone that was not happy …
2.0.6 will be released this week.
1 Like