Recent content by Robert Schuster

I've found it - like often was the problem in front of the screen... I just forgot to add the initiaor name of the 2nd clluster node to the FreeNas list of allowed initors (initiator groups). Now it's working like a charm...

Reply to my own post: I now put "iqn.storage-backup.ctl" aas target name under global configuration at TrueNas and "vmfs" as target name under Targets. Now I can create and delte disks with creating and deleting vm's But - I'm still unable to move disks from local storage of a cluster node...

Funny issue... If I try to create or migrate a disk to the ISCSI storage, I receive the error create full clone of drive virtio0 (store01:vm-252-disk-0) Warning: volblocksize (4096) is less than the default minimum block size (8192). To reduce wasted space a volblocksize of 8192 is...

Last xmas question: Directly in main.cf.in? Where do I have to copy them in that form...

Cool - I'll try that out with my "normal" pmg test installation. Yesterday I've made a new setup with all your other modifications and let point some test domains to that system during the next days. May I've found just one typo in your excellent howto: In the "additional signatures for ClamAV"...

Where does your rbl setting come from? Is this the extract from /etc/pmg/pmg.conf or from the GUI? I'm just wondering what the *2 means?

Hi Alwin, thanks for for the hint but this doesn't solve the challenge at all and yes - I've read the documentation. Unfortunately there was a little typo in my question which makes the whole post more or less nonsense... I wrote mail for domain xyz.tld where I've meant mail from domain...

If I know mail for domain xyz.tld can just be sent from server 111.111.111.111 or 222.222.222.222 how can I reject any mails for whatever@xyz.tld from any other server? Of course the best solution would be a filter rule built at the PMG Interface, but a postfix hack is also welcome regards

Hi Wolfgang, I can confirm - after increasing the timeout in /usr/share/perl5/PVE/Storage/ZFSPlugin.pm (line 52 from 5 to 60) and a restart of the Proxmox VE Host a rollback of the most recent snapshot ist successfull via CLI and GUI! kind regards Robert

Hi Wolfgang, thanks for your help - even it didn't solve the probelm totaly:-) One hint for your further development: The time to deliver the snapshot list takes normaly much more than 5 sec. Even on high performance storage systems under high load and with thousands of snapshots on the zfs...

yes! /usr/share/perl5/PVE/Storage/ZFSPlugin.pm line 52. Increasing to 10 didn't help, than I've tried 60 and it worked for the CLI. CLI via qm rollback vmid snapshot-name works perfect even with RAM, GUI not. Same error than before.

hm... That means wait and see. I've found a 5sec. timeout in the two ZFS related scripts in /usr/share/perl5/PVE/Storage. Increasing this to 10 doesnt help at all but may you have onother place to change it. Increasing the timeout value at ZFSPlugin.pm to more than 10 (I've 60 now) makes the...

just two additional infos: time qm rollback 200 test real 0m12.254s user 0m0.652s sys 0m0.116s (time for this command varies from 5 to 12sec.) time /usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/192.168.100.3_id_rsa root@192.168.100.3 zfs list -t snapshot -o name -s creation ...

Hi Wolfgang, which command do you mean? /usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/192.168.100.3_id_rsa root@192.168.100.3 zfs list -t snapshot -o name -s creation shows the list in ~6sec. (from 5,85 - 6,20) as described in my initial post. The qm rollback <vmid> <snapname> command...