Search results

Hello @andy77 , I think you mean move disk and not live migration...? Live migration -> transfering a running VM from one node to another, storage kept Move disk -> transfering a running VM disk image from one storage to another, node kept Cheers Knuuut

Maybe you have to wipe even more than 500GB on your HDDs. Take a look at this: https://tracker.ceph.com/issues/22354 Cheers Knuuut

This worked for me. Changed title to solved. Thank you!

After removing VMs in "fencing" state from the HA-Manager and re-adding them, I was able to continue with the failed node. Maybe this will help @Nemesis11 too. Business as usual... Cheers Knuuut

I'm affected too. Same error after update on 1 node of 4. 1 node succesful without errors, 1 node failed. No suggestions for solving this at the moment, but if I'll find one, I would post here. Anybody else?

Does this work with images containing a snapshot? Anyway, thank you for the link @Alwin . I'll give it a try.

I've tried to delete the snaphot and the Cluster was unusable for about half an hour,. Even 2 OSDs went down. Fortunately I was able to interrupt the deletion of the snapshot with ctrl+c. After this the cluster went healthy again after a few minutes. This is a 4 node cluster with 32 Intel DC...

That's reasonable. I don't care about the data inside. I just want to get rid of it without killing my cluster. Afaik I can't delete it without removing the snapshot first, or am I wrong?

Hi Community, to create a rbd image of 1T with an object size of 16K is easy. I did it like this: rbd create -s 1T --object-size 16K --image-feature layering --image-feature exclusive-lock --image-feature object-map --image-feature fast-diff --image-feature deep-flatten -p Poolname vm-222-disk-4...

Maybe you're running out of inodes. Check this: df -i

I don't think so, but 30PGS/OSD is a mismatch to your overall PGs of 576 @ 3 replicas. Make a check with ceph osd df tree

man zfs: -c, --compressed Generate a more compact stream by using compressed WRITE records for blocks which are compressed on disk and in memory (see the compression property for details). If the lz4_compress feature is active on the sending system, then the...

512PGs @ 20 OSDs would be nice, but won't match to this configuration.

Maybe not:

Maybe that's a low PGs/OSD rate. Afaik there's a minimum of 75 PGs/OSD, rule of thumb 100PGs/OSD. What kind of HBA do you use? We're running 4 Nodes with Intel 4500 SSDs @ 3000-6000 iops without any noticeable lags so far.

HOW did you want to install ceph? pveceph install is the right way.

Finally, I solved this issue by myself. What I did: Set NTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org in /etc/systemd/timesync.conf on every node. But important was this: hwclock -w several times on every node. No more clock skew issues since...

There is no firewall issue, because ntpq -pn (in case of running ntpd) and also systemctl status systemd-timesyncd.service is giving me positive output.

As I wrote before, I can't reproduce this on other (older) hardware. So my focus is on the current (new) hardware: Intel S2600STB Mainboards with dual Xenons Intel X520-DA2 dual 10Gb SFP+ nics LSI 9341-4i No exotic components at all Any ideas anybody?

I think you mean "NTP=" instead of "Servers=" Anyway, thats like my current configuration. I've already tried this with the ntp servers inside my Datacenter, also with the debian pool servers. This configaration never got "health ok".