Search results

  1. E

    Proxmox 9.1.1 FC Storage via LVM

    The exact cause of this problem is the discard operation. Scenario 1: The guest resides on any source disk structure. When I try to clone this guest into an LVM setup in qcow format, whether the SSD and DISCARD feature on the disk are enabled or not, qcow2 performs discard operations during the...
  2. E

    Proxmox 9.1.1 FC Storage via LVM

    Yes, you are right. For this reason, instead of LVM, perhaps OCFS2 or GFS2 — since it is integrated with Corosync — could be better options that may be supported in the future compared to LVM.
  3. E

    Proxmox 9.1.1 FC Storage via LVM

    Hello @tiboo86 Thank you very much for your feedback and for this extensive sharing. I hope both myself and many others will benefit from it. However, this is an IPSAN system, and the issue I am experiencing is on the FC SAN side. Let’s clarify the OCFS2 topic. Some of our LUNs are used with...
  4. E

    Proxmox 9.1.1 FC Storage via LVM

    I am sharing my multipath configuration and multipath output also storage file, I’m also using OCFS2, and it’s almost perfect. In fact, OCFS2 itself is excellent, but Proxmox forces me to use its own lock mechanism. At the operating system level, OCFS knows these disks are cluster disks...
  5. E

    Proxmox 9.1.1 FC Storage via LVM

    Hi Tibo, If possible, could you share everything? If you have a successful implementation, it could also help others who face issues in the future. By the way, why did you have to tweak the queue-depth and kernel parameters? Do we really need something like that? Also, my issue occurs with...
  6. E

    Proxmox 9.1.1 FC Storage via LVM

    RDM, TCP Offload, RoCE, NVMe-OF, NVMe-oF + RDMA, and Serv-IO (for Ethernet) are all excellent technologies with many benefits. They reduce CPU load and lower access times. However, no matter what they achieve, the real issue is not the connection type or the flow of data, but rather the Ethernet...
  7. E

    Proxmox 9.1.1 FC Storage via LVM

    Most of my 25-year professional career has been spent working with storage devices. A large portion of that involved projects at the government level. I can confidently say that the SAN storage architecture cannot simply disappear. Even today, the largest companies are investing in SDS storage...
  8. E

    Proxmox 9.1.1 FC Storage via LVM

    Years ago, when I wrote about the potential issues of VSAN, many people on the VMware side told me I was talking nonsense. However, developments have shown that SDS architectures are not very suitable for virtualization environments. In a serious enterprise, where several million I/O operations...
  9. E

    Proxmox 9.1.1 FC Storage via LVM

    I tried this as well, since I thought the issue might exist across all cache systems, so I also tested with directsync, but the problem remained the same. The issue lies in the Lock mechanism applied at the Proxmox layer. It’s not only in this part—if you use OCFS2 underneath, you also introduce...
  10. E

    Proxmox 9.1.1 FC Storage via LVM

    General system info : CLONE Speed limit : 300MB/s Wipe Removed Volumes was not selected A time At this point I cloned two machines while DISCARD was enabled on their disks. As shown, the storage wrote very little data, which is normal because TRIM was performed during the transfer. However...
  11. E

    Proxmox 9.1.1 FC Storage via LVM

    It’s an interesting way of answering, maybe it’s just because we speak different languages. Anyway, at the end of the day the situation doesn’t really change. When I work directly with LVM and LVs via direct storage or OCFS2, I don’t encounter the same problems—there’s an ownership aspect here...
  12. E

    Proxmox 9.1.1 FC Storage via LVM

    Hello Friends, First of all, thank you for your answers. However, there is a point we overlooked in the LVM LUN part: this is not a file system, but block storage. Also, LVM thin is not being used in this section. Essentially, the host’s RAM does not hold metadata here (since I use direct sync...
  13. E

    Proxmox 9.1.1 FC Storage via LVM

    Hello, Has anyone successfully implemented a professional Proxmox setup with Fibre Channel (FC) SAN storage? I am not referring to IPSAN, but specifically FC-based SAN. In a clustered environment, I am experiencing significant issues, particularly during cloning, wipe disk operations. The lock...
  14. E

    Suggestion about UI

    I really enjoy using Proxmox, but in a large setup, the number of storages or SDN networks we use can cause serious problems. The "Folder View" is very useful for keeping things organized, but the clutter in the Storage tab and the SDN tab is overwhelming. Instead, if there were a Host tab that...
  15. E

    NoVNC guest mouse gone when upgrade pve-qemu-kvm:amd64 .

    For your information: In the latest update, the following packages were upgraded. Start-Date: 2025-11-11 21:25:38 Commandline: apt-get dist-upgrade Upgrade: pve-qemu-kvm:amd64 (10.0.2-4, 10.1.2-1), libpve-storage-perl:amd64 (9.0.13, 9.0.14), libpve-common-perl:amd64 (9.0.11, 9.0.13) End-Date...
  16. E

    NoVNC guest mouse gone when upgrade pve-qemu-kvm:amd64 .

    Hello, when I upgrade the package pve-qemu-kvm:amd64 from 10.0.2-4 to 10.1.2-1, if I use VNC in the guest system’s Display -> Clipboard section, the mouse becomes unusable in the NoVNC console on the guest. When I downgrade, it works correctly again. To fix the issue, I tried different display...
  17. E

    all server have same disk serial number.

    Hi All, I was found solition on forum " https://forum.proxmox.com/threads/153-hdd-serial-number.23726/" Can you add this serial number change issue to Proxmox User Interface ?
  18. E

    all server have same disk serial number.

    Hi All, I was install 3 Windows 2019 server to my Proxmox host and I was add 3 disk to each server for testing some think. But as your see attached picture file all server have same disk serial nummber, do you know why ? also how I can change if it possible. ( For your information : All server...
  19. E

    [SOLVED] 6.4 Fresh install network config not work.

    Ok this is now work.. Thanks for your assitance.. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. root@node1:~# apt install ifupdown2 Reading package lists... Done Building dependency tree Reading state information... Done Suggested...