Search results

hi @fweber gladly .. I wanted to create a new developer VM and in this case .. exactly this happens, what you told about your issue. An existing device will be reused. Maybe .. you can still use this info: root@fra-corp-pmox-03:[~]: pveversion pve-manager/7.4-3/9002ab8a (running kernel...

hi @fweber don't think so. It does not happen anymore, if you add a filter in lvm.conf like this: global_filter=["r|/dev/zd.*|","r|/dev/mapper/.*-vm--[0-9]+--disk--[0-9]+|"] Most of the issues we had, for create new VMs where no ID was reused. cu denny

Here comes the fancy stuff: Syslog VM: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg2-data 2.7T 927G 1.7T 37% /data/syslog Debian VM df -h /opt/ Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg--data-optfs 777G 625G 121G 84% /opt...

Hi, we don't have snapshots. We delete them, after dangerous work was done: root@fc-r02-pmox-06:[~]: zfs get all rpool/pve-container/vm-100-disk-2 NAME PROPERTY VALUE SOURCE rpool/pve-container/vm-100-disk-2 type...

We had issues in the past .. that the syslog host killed all VMs, with I/O .. so we limited: ostype: l26 scsi0: pve-container:vm-105-disk-0,size=25G,ssd=1 scsi1: pve-container:vm-105-disk-1,discard=on,mbps_wr=40,size=2789377M,ssd=1 we had no issues anymore .. since years .. but the OS was...

hi @aaron I've checked our syslog host .. in the timerange .. a log cleaner started, which cleaned up 300GB. Exactly the same 300GB .. which are "lost" on the rpool and for rpool/ROOT/pve-1. For the syslog host: zfs get volsize,refreservation,used rpool/pve-container/vm-105-disk-1 NAME...

Hello, since a few days, we have on a PVE7 - standalone - host the strange issue, that VMs stuck and not responding (host unreachable) anymore. The root cause seems to be, that the host "/" is getting full: Some envs: Debian Bullseye pve-manager/7.4-17/513c62be Filesystem Size...

Thanks. I will add it :-)

hi, is there a way / hook to make sure, if a VM is purged, that PVE destroys data on the assigned disks first ? I have very often the issue, that data from purged VMs gets available often again, on a new VM. Yesterday I had this issue again, as I've added a 2nd disk to the new VM and create a...

hi, I have this issue also with PVE7 on two different PVE7 clusters, which has ISCSI as shared device. I know this workaround with dmesetup remove .. but I do not really understand, the source of this issue. I can be only a race condition, as it happens not always .. but pretty often for...

Yepp, thanks .. what do you think .. can we let the VMs powered on, or should we power them off ? cu denny

Hi, I've posted also to the Ceph Mailinglist and one answered me .. that: ceph osd pool set db-pool crush_rule fc-r02-ssd ceph osd pool set ssd-pool crush_rule fc-r02-ssd will do the work .. because of "item_name": "default~ssd" .. We will take most parts offline .. as I have no idea ...

Hello, we upgraded our Nautilus till Quincy two weeks ago and wanted to get rid of old settings, which we have since Luminous or older: Splitted SSD / HDD, before Ceph had device-classes: https://www.sebastien-han.fr/blog/2014/08/25/ceph-mix-sata-and-ssd-within-the-same-box/ We executed...

Hello, I have since update from 5 to 6 the problem, that the node-03 wants to send mails to node-01 .. instead of, what is configured on Postfix. We manage the whole Postfix configuration with Puppet, so every node is identical ... except myorigin = fra-corp-pmox-03.example.local Every node...

hi, sorry völlig vergessen ... wir haben ausschließlich eigene Quellen .. daher wundere ich mich ja. cu denny

Guten Morgen, unser Firewall erzählt uns, dass alle Proxmox Instanzen mit 199.232.138.132 über HTTPS reden wollen, was scheinbar zu einem CDN (debian.map.fastlydns.net) gehört, oder gehörte. In der /etc/apt/ ist es nicht zu finden, da wir eigene Repos haben und auch Proxmox selbst hat für...

hi, I tried it with one node and "ignored" the messages: # ceph-volume simple activate --all --> activating OSD specified in /etc/ceph/osd/0-c905557d-3619-4d8b-9da5-cff66fa6340d.json Running command: /bin/ln -snf /dev/sdb2 /var/lib/ceph/osd/ceph-0/block Running command: /bin/chown -R...

hi, I have the exact same problem # ceph-volume simple scan stderr: lsblk: /var/lib/ceph/osd/ceph-5: not a block device stderr: Bad argument "/var/lib/ceph/osd/ceph-5", expected an absolute path in /dev/ or /sys or a unit name: Invalid argument Running command: /sbin/cryptsetup status...

hi @dcsapak , the question is: why not ? :) We can have for every node / backup a different passphrase, thanks to Puppet with Hiera + Eyaml. So it would be very nice, to make it possible, to submit a passphrase without stuff like expect. Also ... maybe you don't want to use the master key ...

hi, because I have no idea to solve it .. I used a workaround with expect: #!/bin/bash # Workaround for input passphrase to proxmox-backup client # Source: modules/profile/files/base # Read the settings and passphrase source /root/.config/proxmox-backup/secrets if [ -f...