Question about SeaweedFS as a JuiceFS object storage backend (why it's not listed in supported backends?)

[hhhizzz]

Hi JuiceFS team,

I'm evaluating a self-hosted deployment and considering SeaweedFS (via its S3 gateway) as the object storage backend for JuiceFS.

I noticed that:

1. The docs mention --storage s3 can be used with S3-compatible object storage.
2. SeaweedFS is not listed in the "Supported object storage" section.
3. There is also an official blog post showing a JuiceFS deployment with SeaweedFS + TiKV.

So I want to ask: why is SeaweedFS not listed as a supported backend?

My main concern is whether this is:

• simply "not in the official test/support matrix yet" (but generally usable), or
• due to known S3 compatibility gaps / behavioral differences that may cause unexpected issues in some JuiceFS workloads (especially under concurrency or failure recovery scenarios).

If there are known concerns, could you share which areas are problematic (for example):

• Multipart Upload (init/complete/abort)
• List / Head / Range Read behavior or consistency
• CopyObject / DeleteObject / overwrite semantics
• ETag / checksum behavior
• path-style vs virtual-host-style endpoint compatibility
• stability/performance under high concurrency

If the status is more like "works, but not officially certified", do you have any recommended:

• SeaweedFS version range
• S3 gateway / filer configuration
• production caveats

I'm asking mainly for architecture evaluation and to avoid compatibility pitfalls, not to challenge the implementation.

Thanks!
您好， JuiceFS team！

我最近在评估本地部署方案，考虑使用 SeaweedFS（S3 Gateway）作为 JuiceFS 的对象存储后端。
我注意到：

1. 官方文档中 --storage s3 说明可以用于 S3-compatible 对象存储；
2. 但“Supported object storage”列表里没有看到 SeaweedFS；
3. 同时官方博客里又有一篇使用 SeaweedFS + TiKV 部署 JuiceFS 的文章。

所以想请教一下，SeaweedFS 没有被列入支持列表，主要原因是什么？

我比较关心的是：

• 这只是因为还没有纳入官方测试矩阵 / 文档未列出，还是
• 确实存在一些已知的 S3 兼容性差异或缺陷，可能会导致 JuiceFS 在某些场景下出现不可预期的问题（例如高并发、异常恢复、边界条件）？

如果是后者，能否帮忙说明一下大概是哪类问题（例如但不限于）：

• Multipart Upload（创建/完成/中止）
• List / Head / Range Read 的一致性或行为差异
• CopyObject / DeleteObject / 覆盖写语义
• ETag / 校验行为差异
• 路径风格（path-style）与虚拟主机风格兼容性
• 高并发场景下的稳定性或性能问题

如果目前属于“可以用但未官方认证”的状态，也想请教：

• 是否有推荐的 SeaweedFS 版本范围或配置方式（S3 Gateway/Filer 相关）？
• 是否有团队不建议用于生产的具体原因？

我提这个问题主要是为了做架构选型，避免踩兼容性坑，并不是质疑功能本身。
如果后续需要，我也可以补充一些实际测试结果（JuiceFS + SeaweedFS 的兼容性验证）供社区参考。

感谢！

[hhhizzz]

To add some context on why we're asking:

We are a mid-sized chemical & energy company in China, and we are currently building an internal AI platform from scratch (including the data/storage foundation). We are now in the architecture selection phase for the storage layer.

We prefer self-hosted, controllable, and maintainable open-source infrastructure, so we are seriously evaluating JuiceFS with different object storage backends, including SeaweedFS.

Our main goal in asking this question is to better understand the support boundary, compatibility risks, and possible roadmap around SeaweedFS, so we can make a more reliable architecture decision.

Also, if there is room for collaboration in the future (for example, compatibility validation, performance benchmarking, feedback from production-like testing, or even contributing development work around SeaweedFS integration), we would be open to further discussion. We hope to be not only users, but also contributors to the ecosystem.

Thanks again for your work and your time.

补充一些背景信息，方便说明我们提问的原因：

我们是一家中型的化工能源公司，目前正在从零开始搭建内部 AI 平台（包括数据与存储基础设施），现在正处在底层存储基座的技术选型阶段。我们希望优先采用可自建、可控、长期可维护的开源方案，因此正在认真评估 JuiceFS + 不同对象存储后端（包括 SeaweedFS）这一组合。

这次提问主要是为了更清楚地了解你们对 SeaweedFS 的支持边界、兼容性风险和可能的演进方向，从而帮助我们做更稳妥的架构决策。

另外，如果未来在 SeaweedFS 适配、兼容性验证、性能测试或相关功能完善方面有合作空间（例如联合验证、反馈测试结果、甚至参与一部分开发工作），我们也愿意进一步沟通。我们希望不仅是使用者，也能成为对社区有贡献的一方。

感谢你们的工作和回复！

[Xuyuchao-juice]

Current status of SeaweedFS: Available, but not included in the official test matrix.
The --storage s3 of JuiceFS can be connected to the S3 Gateway of SeaweedFS, which is technically feasible.
Some users mentioned before that they encountered some issues when using SeaweedFS, such as the lack of security mechanisms and poor support for erasure coding (EC), which led to high usage costs. We are unable to verify these independently. You can further confirm with the SeaweedFS community.

SeaweedFS 当前状态：可用，但未纳入官方测试矩阵
JuiceFS 的 --storage s3 可以对接 SeaweedFS 的 S3 Gateway，技术上可行。

之前有一些用户提到过，他们在使用SeaweedFS对接时遇到了一些问题如：缺少安全机制、对ec的支持不好导致使用成本高等，我们无法独立验证，您可以向SeaweedFS社区进一步确认。