Search results

My guess is when you move drive from storage 2 storage it is registered somewhere (via storage) and that info is used when migrating the container. When the old drive is missing the migration is aborted.

I don't know where this came from subvol-174-disk-0' (via storage). The container only had disk-1 active (or visible anywhere.) So I just backed up the container and restored it on the new node. But now the container has this drive subvol-174-disk-2

I just created a new qemu "node" with vdd drive (zfs) that I created using Proxmox GUI. I had the "Add to Storage" marked when I created the ZFS drive. After that I joined the new node to cluster and tried to move LXC container to it. () 2022-03-04 17:22:18 starting migration of CT 174 to node...

But this is not the reason the first container migration failed because it never had more that 1 drive.

So. For some reason Proxmox tried to migrate the deleted disk-1 and when It did not find it's storage ID it fails the job even though the 2 other disks migrated fine.

root@kvm-p1:~# cat /etc/pve/lxc/601.conf arch: amd64 cores: 2 hostname: pk1.ic4.eu memory: 4096 mp1: vdd:subvol-601-disk-2,mp=/var/backup,size=20G nameserver: 1.1.1.1 8.8.8.8 net0...

Here is a peek in other failure for newer amd64 LXC container. 2022-03-03 00:34:05 successfully imported 'vdd:subvol-601-disk-2' 2022-03-03 00:34:05 delete previous replication snapshot '__replicate_601-0_1645925586__' on vdd:subvol-601-disk-0 2022-03-03 00:34:07 delete previous replication...

That GeoDNS server is OLLLDDD... But some other newer LXC containers also give same error. I'm thinking this has something to do with bug 3376.

root@vm2401:~# cat /etc/pve/storage.cfg dir: local disable path /var/lib/vz content backup,iso,vztmpl shared 0 zfspool: local-zfs disable pool rpool/data content images,rootdir sparse 1 zfspool: vdd pool vdd...

root@vm2401:~# cat /etc/pve/lxc/144.conf arch: i386 cores: 1 features: nesting=1 hostname: geodns1.ic4.eu memory: 512 nameserver: 1.1.1.1 8.8.8.8 net0: name=eth0,bridge=vmbr1,firewall=1,gw=79.134.108.129,hwaddr=7A:54:79:4A:4B:C4,ip=79.134.108.144/26,ip6=auto,rate=2,type=veth onboot: 1 ostype...

Maybe this message is talking about /etc/vzdump.conf Storage ID? Maybe this has nothing to do with ZFS?

The vdd on the new node seems to be scsi1.

I found this on the "old" node.

ERROR: migration aborted (duration 00:00:06): storage migration for 'vdd:subvol-601-disk-1' to storage '' failed - no storage ID specified TASK ERROR: migration aborted I tried to migrate 1 LXC container to another from one (nested) Qemu node to another and got this error. I remember when I...

I couldn't get it to work. Let me know if you figure it out.

Wouldn't it be nice if cluster.fw could be "split" or include links to file(s) that only contained IP address's (or IP/CIDR)? That would make scripting IP list updates really easy. $IncludeConfig /etc/pve/firewall/listname.conf Then we could just "import" fail2ban IP's there with something...

I'm interested in ZFS encryption support (but 2 lazy 2 check.) What is the status of encrypted backups?

Can I just start modifying that list "manually" to add IP's there?

In /etc/pve/firewall/cluster.fw I can see something like this: [OPTIONS] enable 1 [ALIASES] [IPSET Google DNS1] # 8.8.8.8/32 8.8.8.8/32 [IPSET Google DNS2] # 8.8.4.4/32 8.8.4.4/32 [IPSET no2all-list] # Block all - 1 list 2 rule them all 112.85.42.120 112.85.42.121 112.85.42.122

I would like to import list of IP's to Proxmox IPset rule. Any idea how that might be done? I have collected Fail2Ban Recidive list for a while now and would like to import that to a ClusterWide rule set for every LXC container.