Search results

So I wanted to migrate some of my old lxc containers on my very first proxmox cluster (5.3) to my new 7.1 cluster. Created a backup on 5.3, scp it to 7.1 and restore it there. So far so good. However after starting up the container on 7.1 it just hangs at init, i.e. it starts but no shell...

Ok, so on the freenas box without `--direct=1` : # cd /mnt/test1/ssd_pool # fio --size=9G --bs=64k --rw=write --runtime=60 --name=64kwrite --group_reporting | grep bw bw ( KiB/s): min=244247, max=1549668, per=99.60%, avg=444121.98, stdev=329387.20, samples=42 WRITE: bw=435MiB/s (457MB/s)...

I have a strange behavior here and after 2 weeks of fiddling around I am somewhat out of options. There are a proxmox cluster, a freenas box with 8 drive bays and I used the freenas as backup device via NFS. So I had 4 HDDs in the freenas as raidz1. Freenas box is connected via a dedicated 10G...

I would guess those are just control characters used by the CLI to dynamically change the shown numbers, e.g. counting "writing inode tables": 0/80, 1/80, 2/80 etc.

Ok, looks like I figured it out... and it was my fault of course ;) For the test CTs I created it on the first node. Then installed some testing prgs in the CT and to safe time (yeah ...I know ;)) I created a backup and restored it on the other nodes. There I missed that the restored CTs all...

OK, short update after some hours of trial & error... As long as I start CTs only on one node everything is fine. As soon as I start a CT on a second node pings start to behave like above. Cant remember if I tested that on the testcluster...I think I immediately installed the cluster. Probably I...

I set up a test cluster a few months ago with older servers. Everything worked as expected - no problems. So I decided to buy 3 new machines for a production cluster and of course... things start to get strange ;) I have a few public IP /24 networks and mixing them on the old testcluster was no...