Search results

The "out of space" message is confusing. But before that it tells that it cannot auth with the other MONs. Is the cluster healthy except for this one MON? I would then just throw it away and create a new MON instance.

The Proxmox Backup Server is a complex application running multiple processes that need to consume hardware (storage). Why would you want to put that into a Docker container?

Hi, it would be nice to be able to set the Async IO option (aio=) for cloud-init drives in the GUI. We are running a shared storage on a SAN LUN with OCFS2 and we know this is an unsupported setup. Since kernel 6.5 we need the aio=threads parameter for virtual disks. For normal vHDDs this can...

What does top say inside the VM?

What is the output of df -hT /var/log/ceph/?

Set the noout flag: ceph osd set noout. You have to shutdown all clients accessing the storage cluster. This includes mounted CephFS shares and then the MDS daemons. After that you can shutdown all other daemons (OSDs, MGRs, MONs). Restarting is the other way around. After everything works...

You seem to have only one network (10.10.10.1/29). You do not need to specify the cluster_network in the configuration in this case.

This is a question that only you can answer. If you pull many container images into that VM and remove them again not all space on the disk gets directly overwritten. This fills up the virtual disk.

Did you enable the discard option on the virtual disk in the VM configuration? Then you are able to run fstrim inside the VM to free up space on the storage. Otherwise the virtual disk image will only grow.

Are the files /etc/pve/ceph.conf and /etc/pve/priv/ceph/Ceph-VM-Pool.keyring readable?

A container introduces no measurable overhead as the processes within run on the host kernel.

Yes, the service IP is an additional IP address on a network interface of your choice.

You will have to ask Cisco if this software is supported to run inside a KVM VM. Maybe it is only supported on VMWare?

It will resolve the issue that you can remount the NFS share from the same server IP. A running VM on an unaffected Proxmox node will also have to remount the NFS share as the NFS session will not transfer to the new Proxmox node.

Keepalived is responsible to configure a service IP on a network interface on the nodes it runs on. Unfortunately the Proxmox cluster service is not able to do so.

As there is no NFS failover you would always have to remount the share anyway. So there is no point in using a service IP for that. You could install keepalived on the Proxmox nodes and configure a service IP with it.

Create a VLAN-aware bridge interface in Proxmox with the physical interface being a port of it. A bonding interface (link aggregation) could also be the physical port of that bridge. You can then create virtual interfaces for the VMs that either have a VLAN tag configured or not. WIth a...

Do you want to use CephFS inside the VM? Then the VM needs to have access to the Ceph public network. Either directly with a vNIC or routed.

Steht in der Ausgabe von journalctl -u cron etwas erhellendes?

Containers may have their (specific) use cases. But this is not one these.