Search results

  1. D

    Can lvmvdo be added to PVE out of the box?

    Would certainly be nice to have the compression option. I’ve found dedup to be working great, will cost a ton of ram. But.. this option can be disabled with vdo, which leaves us with compression!
  2. D

    New cluster - storage solution

    For a new cluster we are investigating storage solutions. Cluster(s) will be 20 nodes in size, so nothing local and had to do failover and such. Current clusters running on ultra-low-latency nvme, so ceph, NFS and zfs over iscsi ruled out. Been speaking to various suppliers this week. Some of...
  3. D

    [SOLVED] Performance comparison between ZFS and LVM

    Big ZFS fan here as well! But.. if you're running NVME or maybe even SSD's it's not the fastest filesystem around (by design, because a lot of features and safeguards). Even with the patch set included in the latest stable release. This video sheds some light on the issue...
  4. D

    [SOLVED] ZFS resize not "seen" in Debian 11 VM

    Linux sees it, hence the output in lsblk. Filesystem is another animal.
  5. D

    ZFS RAIDZ-1

    No, it's coming. The article mentions Q3.
  6. D

    ZFS RAIDZ-1

    It's coming.. https://freebsdfoundation.org/blog/raid-z-expansion-feature-for-zfs/
  7. D

    Add to existing cluster

    Hi, Question: we're disassembling a proxmox cluster and moving to a new one. What we have left is one node with local storage in this cluster running 5 VM's. We like to physically move this server to a new location and add it to another existing proxmox cluster. Is this possible? What...
  8. D

    Disks not migrated and can't start

    No, shared box was not ticket. The new host doesn't see the logical volumes.
  9. D

    Disks not migrated and can't start

    Hi, I had a server in our proxmox cluster that gave some weird warnings. I decided to reboot it. It had 3 VM's on it. While rebooting it, proxmox decided it was going to live on another host in the cluster. But... it had about 1 TB of local LVM storage on the rebooted server. So .. the old...
  10. D

    Communication failure to storage in GUI

    Hey all, When I look in the interface at the storage (any of the available storage options on this node), I get a "communication failure (0)". VM's running on these storage arrays are fine, it's only a GUI thing. The same storage arrays do show up on other nodes just fine. See attachment. How...
  11. D

    Can't do anything with container

    Hi, I've had an issue where a LXC CT locks for the 2nd day in a row when the backup process starts (snapshot). The backup actually never starts, it just hangs. Killing the backup job brings the CT back online. So I thought that maybe stop/start the CT would help. However.. the stop process...
  12. D

    node semi onlin

    Hi all, I'm having a weird issue with a node. It's online, pingable, but it's half in the proxmox cluster. Proxmox does see it as online, but communication fails. When I reboot it, proxmox does tell me it's offline and it comes back online when the reboot is finished. Output from the node...
  13. D

    IOPS limit

    Hm, that sounds reasonable. Although the 20 times higher IOPS is a difference I can't explain. The array is a RAIDZ2 array, so, yeah, there'll be more writes, but 20 times is still weird. Thanks for checking on the LVM. I didn't have access to a setup to test that.
  14. D

    IOPS limit

    Well, that's the issue. No other background processes are running. The OS is running on a different disk. Furthermore - when I stop the VM, alle IOPS are gone, so we can be sure it is caused by the VM. The other interesting part is that is constant behavior. Right at this moment the VM reports...
  15. D

    IOPS limit

    Hey all, I have a weird issue. I setup IOPS limit to 500 on a KVM VM. It seems to work, from within the VM, see this graph from zabbix: http://imgur.com/a/ZhMO0 So far so good. This VM is the only VM living on the storage platform. If I look at the IO activity on the storage platform, it's...
  16. D

    Add node - reboot all vm's

    Didn't notice anything special really, but I don't have access to the logs anymore, they rotated already. What if I try it again? Would it be beneficial to temporarily turn off HA for the VM's?
  17. D

    Add node - reboot all vm's

    Only thing active on this (physical) network is this proxmox cluster. Fencing is set to software. Not sure about the timers, all default settings anyway. Didn't expect this result, so wasn't logged into any one of the physical boxes.
  18. D

    Add node - reboot all vm's

    Anyone else have an idea on this? I'm really keen to crash my cluster every time I need to add a resource.
  19. D

    Storage migration failing

    Fabian, Upgrade doesn't help. Disabling iothread seems to be the solution. Confirmed this on 4 VM's now. I'm not sure what the impact is of enabling/disabling iothread. What's your take on this?