mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #1] Support Running on Virtual Disks or OSS #2
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @songzhi on GitHub (Feb 28, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/1
Many cloud service applications now run on virtual disks or object storage services. Virtual disks already have data redundancy and reliability guarantees. Can 3FS support running in this mode?
@ppkube commented on GitHub (Feb 28, 2025):
3fs is designed for high-performance workloads and directly manages nvme SSDs and uses RDMA for cross-node communication. Cloud storage provides POSIX filesystem and object store interface, so apparently it's not viable.
One could rent bare metal machines from cloud providers to run 3FS, though.
@songzhi commented on GitHub (Feb 28, 2025):
Yes, but cloud storage also provides block storage protocols that can replace NVMe SSDs in 3FS, and eliminates the need for 3FS to manage redundancy and synchronization. Of course, from a performance perspective, it certainly cannot match bare-metal deployment.
However, if 3FS becomes the "de facto standard" for AI infrastructure, supporting virtual volumes would be meaningful for individuals or small to medium-sized teams who want to learn and use it. They can rent computing and storage resources from cloud providers instead of setting up their own bare-metal servers.
I know that the DeepSeek team has different aspirations, but I am happy to see others exploring more possibilities based on 3FS.
@ppkube commented on GitHub (Feb 28, 2025):
This usually does not speak NVMe (NVMe-oF).
@swpnk commented on GitHub (Mar 3, 2025):
This blog explains how it cannot run on cloud yet. https://open.substack.com/pub/datashot/p/why-3fs-cant-run-on-cloud-yet?r=yr8bh&utm_medium=ios