Search results

It seems correct to me $ ceph versions { "mon": { "ceph version 12.2.4 (4832b6f0acade977670a37c20ff5dbe69e727416) luminous (stable)": 3 }, "mgr": { "ceph version 12.2.4 (4832b6f0acade977670a37c20ff5dbe69e727416) luminous (stable)": 3 }, "osd": { "ceph...

I reverted to kernel 4.13 but the problems still persists.

Hi. In my production/test cluster with Proxmox and CEPH (same nodes) I have a node that I use for testing updates before applying to other servers. Repository pve-no-subscription. After today updates I get in log (just an extract) May 02 17:56:47 pve-hs-3 pvedaemon[4929]: rados_connect failed...

You should already have a maintenance window during which you install kernel updates and reboot server, you should do in that timeframe. Usually changing a ZFS parameter should not cause problems, but you can try on a test machine before.

You should set arc_max (and eventually arc_min) according to the RAM you want ZFS ARC cache to use. In /etc/modprobe.d/zfs.conf, you put the lines: # EXAMPLE ZFS ARC MIN - 512MB options zfs zfs_arc_min=536870912 # EXAMPLE ZFS ARC MAX - 2G options zfs zfs_arc_max=2147483648 Everytime you...

Have you enabled balloning device in the VM config? If you have it disabled, you must shutdown the VM (if it's windows 8 or 10 use shutdown -s -t 0), enable ballooning device in the config and then restart the VM, so you should find the device in the device manager The device is called VirtIO...

You must install the service too, in the Virtion Balloon folder you should run blnsrv -i , it's better to move the balloon folder in a folder on the guest hard disk (if you use it from virtual CD / ISO) Yes

You should install the Virtio Balloon driver and the Virtio Balloon service in the Windows guests

Remove the cdrom line in the VM configuration that maps to the installation iso. In that way the VM can start even if you deleted the ISO.

Install a Windows VM and connect via RDP to that from any machine that you need to.

I had a similar problem and to solve it I just installed a small Debian 9 VM (256MB RAM, 2GB disk) with chrony service installed and servicing NTP on my network

I think it's because zfs pool is not initialized and so it can't find it and /boot partition Try to start with proxmox rescue mode, add the rootdelay=10 to /etc/default/grub in line GRUB_CMDLINE_LINUX_DEFAULT, update-grub and then restart. It's worth a try

In a similar server with a similar setup, I had to add rootdelay=10 to grub command line. Read here: https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Boot_fails_and_goes_into_busybox

I have a similar configuration, a pool made by HDDs and a pool made by SSDs. If the SSDs are correctly recognized, you should see the right device class for the OSDs: $ ceph osd tree ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF -1 8.93686 root default -6 2.94696...

Have you permanent set swappiness in /etc/sysctl.d/ ? Otherwise after reboot it's back to default

After change to /etc/modprobe.d/zfs.conf, did you update-initramfs -u before reboot?

I get email notification from failed pvesr job, ie: Replication Job: 100-0 failed command 'zfs snapshot rpool/data/vm-100-disk-1@__replicate_100-0_1515895201__' failed: got timeout

Can you post the output of qm config 101 What Windows version are you using? I have a lot of VM with various Windows version, all with balooning enabled, virtio drivers installed, balloon service installer inside Windows, and I get no blue screen. You should try to update from proxmox 4.4 to...

Create VPN between the Proxmox sites and the backup site, then use Veeam Endpoint Backup (or similar, I just love Veeam because I use it even in VMWare environments) in Windows VM, that can run incremental backups. Do not open SMB to the internet, tunnel it through a VPN

dmesg -H