bbgeek17's latest activity

  • bbgeek17
    bbgeek17 replied to the thread Proxmox and iSCSI.
    We did a deep dive on this feature in this article: https://kb.blockbridge.com/technote/proxmox-qcow-snapshots-on-lvm/ https://forum.proxmox.com/threads/inside-proxmox-ve-9-san-snapshot-support.169675 Blockbridge : Ultra low latency all-NVME...
  • bbgeek17
    Today must be “remember the old times” day :-) https://forum.proxmox.com/threads/winxp-refuses-to-boot.172058/#post-801693 Just waiting now for an OS/2 Warp question ;-) On a more serious note: digging deeper into the memory banks, if I recall...
  • bbgeek17
    bbgeek17 replied to the thread iSCSI under performance.
    Hi @pmvemf, I realized that I did not answer some of your questions: Our test WAS performed in a cluster. There are no Proxmox specific cluster-aware QoS features that would limit your storage performance. That said, there are some behaviors...
  • bbgeek17
    Digging deep in the memory archives, when/if you have the ISO, you may be able to do a recovery (safe?) boot to see if the disk/installation is visible. You may still need to provide proper drivers/controllers. You may then be able to "repair"...
  • bbgeek17
    Hi @Elleni , PVE is based on the QEMU/KVM virtualization stack. While the Proxmox team makes some enhancements, the fundamentals of QEMU virtualization are universal. Just as ESXi uses VMware Tools for guest integration, QEMU uses VirtIO...
  • bbgeek17
    Hi @spirit, Thanks for your patience. I’ve been meaning to get back to you, but things have been quite busy. On the caching side, I think there may be a bit of misunderstanding around subcluster allocation and the effect of l2_extended=on. In...
  • bbgeek17
    Not only that, but if there are dead DM devices, the lvs, pvs and other scan commands used by PVE will hang. This in turn will cause stats daemon to hang. Having dead devices on the system will lead to unpredictable instability. Blockbridge ...
  • bbgeek17
    Hi @dindon_tv , welcome to the forum. If the steps are executed properly, you should not loose the data. There are many threads on the forum about this, for example: https://forum.proxmox.com/threads/increase-local-lvm-and-vm-disk-size.121257/...
  • bbgeek17
    bbgeek17 replied to the thread Proxmox + shared LVM.
    Normally when using Shared LVM the LV for a particular VM is only active on the node which owns the VM. You should not see a "dev" link for that LVM. From your output, you are using the new QCOW/LVM technology. Keep in mind that it still has...
  • bbgeek17
    Hi @Budgreg , welcome to the forum. Is this how you would describe a system in a ticket you open with Netapp? :-) What does it mean for software to be irritated? :-) This just removes a pool definition from PVE, the OS/Kernel are still very...
  • bbgeek17
    You are welcome, happy we could help. @johannes is correct. The main reason we haven't updated the lvm-shared-storage KB article is that the lvm snapshot bits are not yet ready for production. A considerable amount of focused development and...
  • bbgeek17
    Hi @RonRegazzi , welcome to the forum. Most of your questions regarding best practices should be addressed in your storage vendor's documentation. Many storage vendors recommend using multiple subnets as best practices. That said, you may find...
  • bbgeek17
    bbgeek17 replied to the thread iSCSI under performance.
    @UdoB You are 100% correct and thanks for calling it out! Tables without units are incomplete. I've updated the table headers to clarify appropriate units. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
  • bbgeek17
    It is Perl. It is what PVE does to health check NFS. You can look at two CMD= lines and run those commands manually to see if they fail. Then you can troubleshoot why they fail. You should try testing that it is actually working by doing a large...
  • bbgeek17
    My first impression of the information you provided - you have a network issue. Perhaps an MTU mismatch. Note that PVE health checks for NFS consists of RPC probing (showmount , rpcinfo). Those often use UDP. My next step is to use those...
  • bbgeek17
    If I remember correctly, the official answer is: it should work, but it’s not guaranteed - nobody explicitly tests upgrades between every possible combination of minor in-family releases. That said, the Proxmox team takes great care to avoid...
  • bbgeek17
    Hi @akulbe, What happens when you execute : pvesm status Are you able to "ls"/access the /mnt/pve/VM-Linux and do you see the data there? There is more involved in PVE/NFS relationship than port 2049. Blockbridge : Ultra low latency all-NVME...
  • bbgeek17
    bbgeek17 replied to the thread iSCSI under performance.
    Hi @pmvemf, Following up on this, I asked our performance team to review the kernel iSCSI stack (what you referred to as the "Proxmox native initiator," which is in fact the standard Linux initiator). Our testing with PVE9 showed no functional...
  • bbgeek17
    bbgeek17 replied to the thread Proxmox proxy problems.
    Hi @DJohneys , welcome to the forum. This is not PVE specific but rather standard Linux admistration. There are many ways to do what you want: echo 'export http_proxy="http://proxy.example.com:8080"' >> ~/.bashrc echo 'export...
  • bbgeek17
    bbgeek17 replied to the thread data lost for time window.
    Hi @HaVecko, I don’t have any concrete suggestions for you, mainly because we simply don’t know what happened, only a theory. As a reminder, I’ve never worked with your particular backup vendor. It’s entirely possible that the whole theory is...