Yes, discard is enabled for all disks, however I only enabled it AFTER creating the disks (i.e. they were created without during the import/restore). So this perhaps will only work after moving the disk to a new destination?
Da gebe ich dir recht, und ja ich war etwas polemisch. Trotzdem, mit ZFS musst du im Notfall nicht den exakt selben RAID Controler finden, nur um dann zu merken, dass er das RAID trotzdem nicht mehr funktioniert. Bei ZFS, kannst du im schlimmsten...
Well, you can put different sized disks into one pool. "Striped". This is NOT recommended because it removes some very important features!
A mirror (and that's what we mostly use in PVE context) needs two (or more) same sized disks.
You can...
I have, that's why I'm here. Been doing IT for 30 years. I do a lot before I ask for help. There are a few different versions, even this particular model can come with two different CPUs. The only info or videos I can find are related to the...
Hi dakralex! Thanks for the help so far!
After some hardware shuffles, they are now `01` and `0b`. `0b` is the troublesome one. `lspci` provided for both.
root@nasty:~# lspci -s 0000:01:00 -vvnnk
01:00.0 Serial Attached SCSI controller [0107]...
If the VM stays the same, moving the VM between nodes does not affect any licensing agreement. As long as the PC (virtual or dedicated) stays the same, the underlaying hardware or hypervisor does not matter.
Does it work when you stop your PVE-Firewall ( systemctl stop pve-firewall ) ? Usually outgoing connections are always allowed, even with the firewall enabled (and E/R incoming connections aswell).
I think the issue is not the vdev redundancy level. The same would happen even with the following pool layout which should be sane.
3xMirror special device
Raidz3 8xhdd vdev
ZFS 2.4 specially allow zvol write to land on the special vdev so it's...
This function already exists. You can edit the notes template for each backed up VM/Container at your will. Then, within the name, you have a NOTES section where you have exactly what you are looking for.
example output:
# ./reboot_by_tag.sh k-core
next: k-core
- rebooting 220 (via pve-c)
- vm has started back up, pausing a moment to give it a little time to start things
next: k-core-c1
- rebooting 221 (via pve-a)
- vm has started back up...
# cat reboot_by_tag.sh
#!/bin/bash
# display syntax if no parameter
if [[ "$1" == "" ]]; then
echo "Will reboot all hosts with specified tag."
echo ""
echo "Syntax:"
echo " $0 <tag>"
exit 0
fi
# use to get ip of proxmox host...