Search results

Was Claude so produziert: https://cyberplace.social/@GossiTheDog/116080909947754833

Ich würde selbst bei genauester Formulierung einer solch stochastischen Maschine nie den produktiven Betrieb anvertrauen.

OSDs have a minimum allocation size (min_alloc_size) of 4096 bytes which is configured at creation time and cannot be changed afterward. But this mostly affects small files.

Ich verstehe nicht, warum niemand mehr selber lernen möchte.

No, the separation of the Ceph public and cluster (not private) networks has nothing to do with security. The cluster network is there to transport replication and recovery traffic between the OSD nodes. It can be configured if there is a separate physical network available that provides more...

All Ceph daemons register in the CRUSH map wih exactly one IP and one port. You can have multiple public networks in the config but this is for the case where different hosts of the Ceph cluster are in different IP networks. It is not practical to have one Ceph host with IPs from multiple public...

So /dev/sdi already has one block.db? And no volume group with a logical volume for it? How was the first block.db created on /dev/sdi?

Bau Dir doch ein Skript, das via API die Einstellungen vornimmt. Dann hast Du es reproduzierbar.

If you need more than RBD (block storage) and CephFS (file storage) from your Ceph cluster you should look into not deploying it with the Proxmox tools.

We are running a cluster of 8 Proxmox VE nodes with OCFS2 on a SAN LUN since several years. It works but it is not officially supported. There were some issues even with OCFS2 in recent kernels as the development of OCFS2 seems to have come to a halt. The performance of OCFS2 is very good when...

Die Dateien unterhalb von /var/cache mögen zum Teil volatil sein. Die Verzeichnisstruktur ist es sicher nicht. apt clean hätte unfallfrei aufgeräumt.

NVMe-oF in Ceph works from version 20 onwards. Do not try it with reef or squid. And AFAIK you need the cephadm orchestrator to configure it.

No, as soon as there is no quorum any more between the MONs, i.e. the majority of MONs do not see each other, the cluster will stop working. And for the number of MONs: The cephadm orchestrator deploys 5 by default for the reasons I outlined: https://docs.ceph.com/en/latest/cephadm/services/mon/

The current recommendation from the Ceph project is to run 5 MONs. With only three MONs you run into a high risk situation after losing just one MON. Losing another and your cluster stops. With five MONs you can loose two and the cluster will still work.

Is a specific pool affected by shutting down one host? Your CRUSH rules are a wild mix.

Please post the output of ceph status ceph mon dump ceph config dump ceph osd df tree ceph osd crush rule dump ceph osd pool ls detail from each node: ip addr show

Die Windows-VM benutzt virtio-scsi-single?

GlusterFS is basically dead.

You may have a look at the DRBD integration for Proxmox: https://linbit.com/blog/linstor-setup-proxmox-ve-volumes/

Before re-inserting the NVMe you should remove the remains of the LV which will still be n. the kernel after you pulled it. Only after that the LV will be re-attached cleanly. This is clearly an edge case as normally you will pull a defective drive and replace it with a new empty one where a new...