Search results

Note that in recent kernel (>= 4.7), "discard" mount option is now async, so you can enable it without write penality. (and no more fstrim cron is needed)

you can try to boot on kernel 4.4 from old proxmox, it should works. (just to compare). Which network card do you use ?

hi, do you use same hardware before and after bluestore convertion ? (nvme was used for filestore journal ?)

It's a rocksdb bug with sse4.2 . cephs devs have make a pull request in rocksdb github https://github.com/facebook/rocksdb/pull/2807

for ceph, cache=writeback can improve sequential write (but increase latency for read). you can use discard with ceph && zfs, no problem.

do you have installed the balloon driver before trying to start the service ?

It's impossible to do it in 1 cluster. I think corosync have a hardlimit in code, around 100 nodes. (and this need a lot of tuning of corosync) I never have tested more than 20 nodes. I think the proxmox plan was to be able in the future, in 1 interface, to manage multiple clusters. But...

step 4->6 : use new "qm importdisk" from proxmox5 ;) I'll directly read the vmdk and write it to destination storage (zfs, ceph, ...), without intermediate step.

If it's really a proxmox upgrade bug, I think it can be only 2 thing : qemu version, or kvm version (host kernel module). Maybe can you try to install proxmox 4 pve-qemu-kvm and pve-kernel deb package on your proxmox 5 installation try first with qemu: ----------------------------- wget...

systemctl (status|stop|start) ceph-mon@0 (remplace 0 with id of the monitor , same for ceph-osd, .. )

Note that qemu share a single thread by default, for disk,nic,.... maybe can you try to enable iothread on disk ? (virtio or scsi + virtio-scsi-single controller). (note that it's not yet compatible with proxmox backup)

>>While normal usage I have ping response times between 20-35 mSec on my local bridge Is it really from host bridge to to vm ? I'm around 0.1ms from host bridge to guest vm. more than 1ms locally is really anormal.

Maybe related: https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg03973.html

does the back migration (newnode->oldnode) works if you only update pve-qemu-kvm package on oldnode ? (apt-get install pve-qemu-kvm should be enough to upgrade only qemu) Note : And just to be sure, the vm has not been stop/start on new node, before trying migrate back ? Because in this...

apt-get upgrade only upgrade installed packages apt-get dist-upgrade also install new packages from dependencies. So you should always use dist-upgrade, or it could give you breakage like this.

watchdog is now disable by default, but in proxmox 4.1 only. Do you have done last updates ?

you should enable igmp snooping on your network switch to avoid mutlicast packets from other cluster coming to theses nodes. (also be carefull to not use same clustername, because the multicast address is generated from clustername)

you can try to do a "ps -aux" on host, and compare qemu command of proxmox vs ubuntu.

Is the server bios and cpu microcode update on last version ?

Hi, Can you post result of "ipmitool mc watchdog get" ? (ipmitool package need to be installed) what is your server model ? which watchdog do you use ?