Search results

If you are happy - we are happy. You can mark the thread as solved by editing the first post and adjusting the subject prefix. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @zav0k , The configuration you describe is pretty common. It works well when configured properly. There are many resources online that can help with your configuration, but nothing replaces hands-on work and deep understanding of each step. We wrote an article that may be helpful with high...

It didn't seem that either reporter filed a bug with PVE. You may want to do so. I doubt the backend SAN version change will have any affect on this behavior. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

https://forum.proxmox.com/threads/move-storage-fails-with-qemu-img-convert-invalid-argument.179123/ https://forum.proxmox.com/threads/proxmox-cloning-corrupts-the-target-image-extensive-analysis-included.177841/#post-826710 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

There were recently some bug fixes in this area. Make sure you are running with the latest code. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

You are missing critical step of creating a file system, as I've described in your other thread. However, you should not be creating regular file system on your shared block device. I'd recommend continuing to use your thread vs necroposting into unrelated ones. Blockbridge : Ultra low...

Hi @williamss159 , If you want to store ISO, which are files, you need a filesystem. Filesystems can be created on top of a raw device , partition, or LVM slice. However, cluster of nodes is a special case. It requires a cluster aware filesystem. Using regular filesystem will cause data...

You are welcome. That is exactly the topic of the discussion in the provided link. Note that this is an in-VM configuration, outside of the scope of PVE and this forum. There are many other discussions and tutorials on mounting CIFS share on boot. Good luck Blockbridge : Ultra low latency...

Sounds like you just need to map CIFS share from VM directly to NAS. Your application may even have a wizard to do so. If it does not, add the mount to /etc/fstab https://askubuntu.com/questions/157128/proper-fstab-entry-to-mount-a-samba-share-on-boot Blockbridge : Ultra low latency all-NVME...

If you see the ACK leaving the physical port, then it is likely that the problem is further down the line in the infrastructure. Have you contacted OVH with your issue/findings? Do you have console access via OVH? Perhaps you can try to "ip link down/up" the ports as an experiment. It sounds...

@williamss159 , what do you mean by LCM? Perhaps LVM? LVM is a block type storage , there are no files or directories. If you follow one of many guides, including the one I posted earlier, PVE will be able to slice and dice pieces of overall LVM pool into smaller block level pieces it can use...

You are welcome! Happy to hear you got it going. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Here is another article that may be helpful: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/ Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

I just realized that the post you referenced is a summary of our KB article :) Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for the link @katti. It so happens that we, at Blockbridge, are somewhat familiar with how Veeam operates: https://forums.veeam.com/proxmox-ve-f79/fyi-potential-data-corruption-issue-with-proxmox-t95796.html The forum post you referenced does not spell it out, but the changes in PVE...

Hi @katti, You do not need storage snapshots for Veeam backup of any type of storage pool in PVE. 1 Yes, you can have snapshots with FC SAN by using new tech-preview feature: https://forum.proxmox.com/threads/proxmox-ve-9-lvm-snapshot-feature-still-tech-preview.175210/ 2 Using QCOW on any file...

TBH, layering QCOW on a newly added LVM extent without manually zeroing it first seems like a recipe for trouble. This approach is unpopular because it slows provisioning, but it is the safer option. When QCOW is placed on a filesystem, zeroing is implicitly handled by the filesystem through...

Hi @medichugh, Best way is to examine the specified files and remove one of the duplicate references, so only single reference remains. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

You are welcome. You may also find this article interesting as well https://kb.blockbridge.com/technote/proxmox-qemu-cache-none-qcow2 https://forum.proxmox.com/threads/understanding-qcow2-risks-with-qemu-cache-none-in-proxmox.175933/ I do not believe this option will help you, based on the man...

Unfortunately, this is a known issue that we pointed out a while back : https://kb.blockbridge.com/technote/proxmox-qcow-snapshots-on-lvm/#data-consistency-and-information-leak-risks https://forum.proxmox.com/threads/inside-proxmox-ve-9-san-snapshot-support.169675/#post-791725 Blockbridge ...