谢谢建议，暂时还是先观望一下 Alist 后续发展，临时用一下其他的 S3 服务。或许之后考虑用推荐的 minio 自建一个 S3，折腾这个云盘主要是想多个云盘备份。

更新下进展。

查看了下 alist 和思源两边的日志，首先是思源这边，主要还是下面这一段类似内容的日志。

E 2024/06/20 17:49:15 sync_lock.go:159: upload lock sync failed: NoSuchKey: 
	status code: 404, request id: 0E04EEA5265D35EF, host id: MEUwNEVFQTUyNjVEMzVFRjBFMDRFRUE1MjY1RDM1RUYwRTA0RUVBNTI2NUQzNUVGMEUwNEVFQTUyNjVEMzVFRg==
E 2024/06/20 17:49:15 repository.go:1307: sync data repo failed: lock cloud repo failed

以“upload lock sync failed: NoSuchKey”和“同步失败：锁定云端同步目录失败，请稍后再试”为关键词搜索了一番，有发现思源有相关问题，不过是 webdav 协议的。相关的解决方法也没什么用。

再一个是 alist 这一边，日志重复出现了“serve s3: Access Denied”的内容。

INFO[2024-06-20 09:37:12] serve s3: Access Denied: 172.17.0.1:35696 => / 
INFO[2024-06-20 09:37:45] serve s3: Access Denied: 172.17.0.1:35696 => / 
INFO[2024-06-20 09:37:45] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync?response-cache-control=no-cache 
INFO[2024-06-20 09:37:45] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync?response-cache-control=no-cache 
INFO[2024-06-20 09:37:46] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync?response-cache-control=no-cache 
INFO[2024-06-20 09:37:46] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync?response-cache-control=no-cache 
INFO[2024-06-20 09:37:46] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync 
INFO[2024-06-20 09:37:46] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync 
INFO[2024-06-20 09:37:46] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync 
INFO[2024-06-20 09:37:47] serve s3: Access Denied: 172.17.0.1:35696 => /siyuan/repo/lock-sync 
INFO[2024-06-20 09:38:40] serve s3: Access Denied: 172.17.0.1:35696 => / 
INFO[2024-06-20 09:38:55] serve s3: Access Denied: 172.17.0.1:35696 => / 
INFO[2024-06-20 09:46:12] serve s3: Access Denied: 172.17.0.1:59562 => / 
INFO[2024-06-20 09:49:15] serve s3: Access Denied: 172.17.0.1:58710 => /siyuan/ 

但是以日志时间连续来说，并不是每次出现了这个日志，在 alist github 的 issues 上搜索了“serve s3: Access Denied”、“S3”、“对象储存”这几个关键词，发现了个比较在意的问题。

• 对象存储无法上传文件夹，会变成文件
• 对象存储不能支持上传多级文件

其中提到 alist 的对象储存存在一个可能的 bug，有相关人员也肯定了这个结果。

到现在为止，怀疑的对象处在 alist 上，暂时静观发展，等待问题修复。先使用一下 cloudflare R2 提供的 S3 储存服务。