Recent content by NdK73

Ah, ok. So if I have 3 rooms, 3 nodes per room and size=5 I can be sure that downing a single host won't take down more than one replica. Downing a room, on the other hand, will take down up to two replicas. Right? I'm actually thinking about adding osds to have a "capacity pool" on hdd and...

Not sure I understand. If there's one replica per room, and each host can only be in one room, two replicas cannot be on the same host...

Tks a lot! Couldn't see it. No idea WHY it's 2 instead of 3... Now I've run ceph osd pool set main_3 size 3 and it started recovery... It won't finish before virt3 comes back online, but I hope it will prevent a future down.

Yes, the cluster was healthy. Maybe the pgs are not active because they've never been used? root@virt1:~# pveceph pool ls --noborder Name Size Min Size PG Num min. PG Num Optimal PG Num PG Autoscale Mode PG Autoscale Target Size PG Autoscale Target Ratio Crush Rule Name %-Used...

The cluster was healthy. And virt3 node is still down :( The remaining nodes (virt1 and virt2) can see each other and are actually recognized to form a quorum: root@virt1:~# ceph -s cluster: id: a76df3b3-8b6d-42da-a901-47e80c660df4 health: HEALTH_WARN 1/3 mons down...

That's what I understood, too. But practice says it does not work. So I'm trying to understand why and what can I do to make it work ASAP...

Well, I'm OK for ceph to be degraded for some time: it should just continue writing to the other two copies! That's the whole reason to keep 3 copies: continue to write even if one goes down! Else I'd choose just 2 copies, so that if a node goes down the cluster heals on the remaining two. With...

That seems quite unrelated: it just happens that the power outage took down both virt3 and PBS. Once I disabled PBS storage, virt1 answered again.

That's what I thought. If only Proxmox thought the same... :) There's a monitor on each host, as default setup, and the quorum is met. Moreover, now the Proxmox interface hangs when trying to access Ceph dashboard. Paint me even more confused! Actually ceph does not say anything about being...

Hello all. I deployed a 3-node cluster w/ ceph, one node per server room, to be able to keep working when (not if) one of the rooms goes down. Too bad it seems that Proxmox stops IO even when ceph cluster would still be working: the result is that a downed room blocks all the VMs in the cluster...

Tried looking at it but IIUC I'd need 3 new vdevs with the same raidz3 layout just for metadata... One SSD can probably be added, the second could even be hammered in, but 3 or more is not possible and 18 would be plain ridiculous.

I sometimes click the 'v' next t othe pencil for the latest backup and it gets marked 'ok'. At next gc I'll see if the verified ones become corrupt or not. But it seems pbs does not handle well big backups (like the one containing a 32TB disk): nearly 3 days for a complete backup, way more for...

Here it is. But packages got updated yesterday, after fixing the backups. root@pbs:~# proxmox-backup-manager version --verbose proxmox-backup 3.2.0 running kernel: 5.15.131-2-pve proxmox-backup-server 3.2.7-1 running version: 3.2.7...

Hello. Seems the job for prune & GC does not account for data generated by concurrent backups. In my case GC takes 17 days (on 24 16TB SAS disks configured as a single pool containing 3 RAIDZ3 - it's simply economically unfeasible to have the same amount of storage on SSD just for backups!)...

Handle automated reinstallation of the OS, initiated by the guest itself. But not every boot have to be a reinstall. Changing the boot order is usually the easiest thing to do.