Search results

CEPH can only do one network per front and back, so you won’t be able to do redundancy unless you can do LACP across both physical switches.

How much ram does the host machine have? How much ram are you assigning to the VM?

If you want to use CEPH to storage the files you have the option of CEPHFS or RBD as you state. Thing with RBD or any FS once you get big you get negatives such as long FS scans and many other things if you ever have an issue down the road, the benefit of cephfs is all that stuff is running in...

Need some more information to help.. What do you have setup pool wise on the disks? Replication? Erasure Coding? How are you mounting the storage to the backup server? Is ceph in a fully healthy state? If you do tests locally on a box running Proxmox/CEPH what speeds do you get then?

SSD's usually wear from writes, depending how much writes you expect your VM's to do will decide on what SSD's you should get. Samsung make some consumer SSD's from EVO -> PRO ($$ -> $$$), as others have suggested keep Proxmox running on the RAID 1 HD and add two SSD's in RAID 1 and migrate the...

If the cluster is separate can’t see any reason why as Proxmox really isn’t doing any interaction directly with CEPH it would be down to the version of QEMU/tools and if there was any breaking changes with older versions of CEPH.

If you have discard enabled it will zero the whole new disk first, hence the delay / high I/O time. If you can your better to disable discard, reboot and then migrate. This is a current limitation of QEMU and not PVE

During the migration it will show the progress at each stage and time taken e.t.c You should be able to find the migration in the tasks at the bottom of the portal, if you scroll through it should give you a good idea of what part took a long time to complete, fact the VM is fairly small disk...

Thanks just logged it : https://bugzilla.proxmox.com/show_bug.cgi?id=3998

Firstly sorry if this is the wrong place to post this. With CEPH within Proxmox is there the ability (that I am missing where) / planned feature for the following: Set folder quota within cephfs (Available within the CEPH Dashboard itself) Create / Manage Ceph users (currently not available...

Hey, Setup a CEPH cluster within PVE, all working fine. Looking to use the cephfs-top command but getting the following error: cephfs-top cluster ceph does not exist Is there a way to find the cluster name that was set by PVE as I can't seem to see it anywhere.

Okie fixed for real this time with apt reinstall librados2=15.2.13-pve1~bpo10 libradosstriper1=15.2.13-pve1~bpo10 ceph-common=15.2.13-pve1~bpo10 librbd1=15.2.13-pve1~bpo10 python3-cephfs=15.2.13-pve1~bpo10 python3-ceph-argparse=15.2.13-pve1~bpo10 python3-ceph-common=15.2.13-pve1~bpo10...

So I thought it was fixed, but just went to run the upgrade and is the same message. If I try and remove the ceph-common package it also tries to remove the proxmox-ve package, how can I clean up the old CEPH packages without removing the proxmox-ve package?

Yes, I run a separate ceph cluster to Proxmox, some nodes I have installed some of the basic CEPH CLI packages via the Offical Ceph repo, I have removed them ceph packages and is now working as expected. Thanks

pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-5 pve-kernel-helper: 6.4-5 pve-kernel-5.4.128-1-pve: 5.4.128-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.78-2-pve: 5.4.78-2 ceph: 15.2.14-1~bpo10+1...

I have updated a few 6.x nodes to 7.x fine. I have one node that had the PVE Test repo added to test a newer kernel previously. When trying to update this node I get the message: W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W: (pve-apt-hook) W: (pve-apt-hook)...

apt update Hit:1 http://deb.debian.org/debian buster InRelease Hit:2 http://deb.debian.org/debian buster-updates InRelease Hit:3 http://security.debian.org/debian-security buster/updates InRelease Hit:4 http://mirror.hetzner.de/debian/packages buster InRelease Hit:5...

I have a server running 6.4.x When I run apt update && apt-dist upgrade it trys to remove promox-ve along with some other packages apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were...

If your CEPH cluster is separate to Proxmox then the ceph.conf file is only every read by the QEMU RBD process for any client specfic entries. Will have 0 impact on any separate CEPH cluster.

Running just the pure OS on the SSD via USB should be no issues (disable log's and everything else not required), however as Alwin said, if you also need to store the MON data on this USB disk then you may end up with issues. However, if you can store your MON(s) on a separate server then no...