I am not using the sub-folder syncing that often and always come around it every now and then as you can see by the way how I react to this topic
So here are some further findings.
Thanks again for your tip from back then.
I don’t think though that shoeper meant that this error is connected to the file permissions in the seafile directory. I think he meant a a permission check within Seafile client / Server.
Also I checked and the entire seafile data / storage directory is owned by my “seafileuser”.
So the chown solution seems not applicable for my issue.
So I did some other stuff:
I did an fsck on the library that I can not sync, which did not give an error.
Starting seaf-fsck, please wait ...
[02/06/19 10:20:51] fsck.c(593): Running fsck for repo 6789sdrg-d534-40b8-8e9b-bhgfjkdelnhjk.
[02/06/19 10:20:51] fsck.c(413): Checking file system integrity of repo P099(4473f86e)...
[02/06/19 10:47:55] fsck.c(657): Fsck finished for repo 6789sdrg.
seaf-fsck run done
So no issues from FSCK side.
It looks like a permission bug to me, But I don’t know where it comes from and how to solve it…