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

推荐订阅源

S
SegmentFault 最新的问题
Google DeepMind News
Google DeepMind News
G
Google Developers Blog
Martin Fowler
Martin Fowler
MongoDB | Blog
MongoDB | Blog
月光博客
月光博客
Jina AI
Jina AI
宝玉的分享
宝玉的分享
人人都是产品经理
人人都是产品经理
D
DataBreaches.Net
V
V2EX
WordPress大学
WordPress大学
T
The Blog of Author Tim Ferriss
Last Week in AI
Last Week in AI
B
Blog
博客园 - 叶小钗
小众软件
小众软件
Stack Overflow Blog
Stack Overflow Blog
P
Proofpoint News Feed
A
About on SuperTechFans
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Y
Y Combinator Blog
Microsoft Security Blog
Microsoft Security 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
TPM State problems with CEPH / Proxmox 9.2
invalid@exam · 2026-06-02 · via Proxmox Support Forum

Hi,

Proxmox version 9.2.3, CEPH Tentacle 20.2.1

I've came across an issue with CEPH and TPM State disks. I've created a VM that is located on ceph rbd pool. The VM has an additional 4MB disk with tpm state. The vm doesn't start with following error:

Code:

In some cases useful info is found in syslog - try "dmesg | tail".
rbd: sysfs write failed
TASK ERROR: start failed: can't map rbd volume vm-123-disk-2: rbd: sysfs write failed

CEPH is healthy and is running a hundred of other VMs (but with no TPM state).
When I migrate the ceph mini volume to local-lvm storage the VM starts with no issue.

I wonder if I miss something in the ceph config or just came across a bug in newest version?

Yes, I'm using dual stack - my main network is ipv4 and the network for the ceph cluster is ipv6. This might be the similar issue as in the link you sent above. I'd very grateful if you give me any advice how to configure it better. Dual stack is always some kind of a problem :-)

I have also problem deploying MDS servers for CEPHFS. It looks like it deploys, MDS servers get the ipv6 addresses but when I try to add CephFS at datacenter level it fails with timeout.

When I check the ports on the pve host MDS listens on ipv4 only:

Code:

tcp   LISTEN 0      512                  0.0.0.0:6867       0.0.0.0:*    users:(("ceph-mds",pid=907329,fd=21))                                                             
tcp   LISTEN 0      512                  0.0.0.0:6866       0.0.0.0:*    users:(("ceph-mds",pid=907329,fd=20))                                                             
tcp   LISTEN 0      512                        *:6865             *:*    users:(("ceph-mds",pid=907329,fd=19))                                                             
tcp   LISTEN 0      512                        *:6864             *:*    users:(("ceph-mds",pid=907329,fd=18))

ceph.conf

Code:

[global]
        auth_client_required = cephx
        auth_cluster_required = cephx
        auth_service_required = cephx
        fsid = 145705a8-549b-408e-8d55-7f7407781833
        mon_allow_pool_delete = true
        mon_host = fd69:beef:cafe::551 fd69:beef:cafe::552 fd69:beef:cafe::553 fd69:beef:cafe::555 fd69:beef:cafe::554
        ms_bind_ipv4 = true
        ms_bind_ipv6 = true
        osd_pool_default_min_size = 2
        osd_pool_default_size = 3

[client]
        keyring = /etc/pve/priv/$cluster.$name.keyring

[client.crash]
        keyring = /etc/pve/ceph/$cluster.$name.keyring

[mon.pv1]
        public_addr = fd69:beef:cafe::551

[mon.pv2]
        public_addr = fd69:beef:cafe::552

[mon.pv3]
        public_addr = fd69:beef:cafe::553

[mon.pv4]
        public_addr = fd69:beef:cafe::554

[mon.pv5]
        public_addr = fd69:beef:cafe::555

storage.cfg

Code:

dir: local
        path /var/lib/vz
        content vztmpl,iso,backup

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

rbd: np03
        content rootdir,images
        data-pool np03-data
        krbd 0
        pool np03-metadata