惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
量子位
大猫的无限游戏
大猫的无限游戏
小众软件
小众软件
J
Java Code Geeks
B
Blog
V
V2EX
博客园 - 三生石上(FineUI控件)
Blog — PlanetScale
Blog — PlanetScale
aimingoo的专栏
aimingoo的专栏
Y
Y Combinator Blog
F
Fortinet All Blogs
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
A
About on SuperTechFans
D
DataBreaches.Net
阮一峰的网络日志
阮一峰的网络日志
博客园 - Franky
H
Help Net Security
宝玉的分享
宝玉的分享
Martin Fowler
Martin Fowler
酷 壳 – CoolShell
酷 壳 – CoolShell
MongoDB | Blog
MongoDB | Blog
L
LangChain Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Clarification about Ceph suitability for a 2-node storage...
invalid@exam · 2026-06-27 · via Proxmox Support Forum

Hello Proxmox community,

I would like to ask for a technical clarification regarding the use of Ceph in a Proxmox VE architecture with only two storage nodes.

We are currently evaluating a virtualization infrastructure where the target architecture is based on:

  • 2 Proxmox VE nodes used for virtualization and storage
  • 1 additional witness/quorum node without storage OSDs
  • Synchronous replication between the two storage nodes
  • High availability for virtual machines
  • Split-brain protection
  • Continuity of service in case one storage node fails

The proposed storage solution is Ceph. However, I would like to confirm whether Ceph is really suitable for this kind of production architecture.

My understanding is that Ceph generally requires at least three storage nodes with OSDs in order to provide proper high availability and data redundancy. With only two storage nodes, using a replication size of 2 may lead to problems when one node fails, because Ceph may not be able to continue write operations safely while maintaining the required number of replicas. On the other hand, reducing min_size to 1 may allow degraded operation, but it also means that data may temporarily exist with only one valid copy, which could increase the risk of data loss.

Therefore, I would appreciate clarification on the following points:

  1. Is Ceph recommended for production with only two storage nodes and one witness/quorum node without OSDs?
  2. Can a witness/quorum node without storage OSDs replace a third Ceph storage node from a data availability point of view?
  3. In case one of the two storage nodes fails, can Ceph continue to provide safe write operations while still maintaining proper data redundancy?
  4. Is the recommended Proxmox/Ceph architecture for production high availability based on at least three full storage nodes with OSDs?
  5. Would you consider a 2-node Ceph storage architecture suitable for a production virtualization platform requiring HA, or should another SDS/vSAN solution designed for 2-node deployments be considered?

The goal of my question is to assess whether Ceph is technically compliant with a target architecture limited to two storage nodes plus a witness/quorum node.

Thank you in advance for your clarification and recommendations.

Best regards,