Re: Which technology to choose for shared primary storage

Hey João Thank you for your feedback! "I would say that the easiest to deal with and most compatible protocol is NFS" This is also my impression. I want to keep the solution simple and not add additional layers - so, will stay with NFS and not use stuff like iSCSI, FC and Ceph. Best regards Pa

Re: Which technology to choose for shared primary storage

Hello, Paketix I would say that the easiest to deal with and most compatible protocol is NFS. The next paragraphs assume we are talking about using these storage types with KVM as the hypervisor. The "problem" with FC and iSCSI, when using KVM, is that you'll need an extra layer on top of

Re: Which technology to choose for shared primary storage

Correct Apache CloudStack documentation links: 1. Https://docs.cloudstack.apache.org/en/4.22.0.0/conceptsandterminology/choosing_deployment_architecture.html#hypervisor-support-for-primary-storage

Re: Which technology to choose for shared primary storage

Hi, My understanding is that primary storage in CloudStack mainly depends mostly on what the hypervisor supports, and not CloudStack itself. The table here in the official CloudStack documentation that shows the supported storage types per hypervisor, including FC for most of them: https://d

Which technology to choose for shared primary storage

I am new to CloudStack and could need some help/advise regarding which technology to use to implement my shared storage (primary storage). Having some FibreChannel stuff in the lab this could work well. ... but I am concerned that this is not the direction CloudStack is developing into. So: - N

Re: QCOW2 on NFS shared storage

Thank you for all the replies. I will answer all the additional questions I got here: 1. Hard vs soft mount. * It originally was a hard mount and I moved it to a soft mount as part of troubleshooting. * I did increase the retries by 1. I will increase the timeout and see if it help

Re: QCOW2 on NFS shared storage

IMO, TrueNAS enterprise on their hardware seems to involve re-importing the pool and restarting the NFS service during a failover. This means that the NFS client cannot automatically reclaim its state to the new NFS primary, unlike the ordinary Linux Pacemaker NFS cluster, which can handle clien

Re: QCOW2 on NFS shared storage

Also, make sure you disabled nfs4 delegations. This can cause all kind of weird problems. Maybe thats the reason why nfs3 is working fine for you https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4DelegationMandatoryLock Am 14.11.25, 09:58 schrieb "Jürgen Gotteswinter" mailto:juergen.gotteswi

Re: QCOW2 on NFS shared storage

Have you tried mounting your shares with „hard“ instead of „soft“? Reducing timeo and retrans might also improve your situation. Von: Marty Godsey Antworten an: "[email protected]" Datum: Freitag, 14. November 2025 um 09:45 An: "[email protected]" Betreff: Re: QCOW2 on NFS

Re: [D] Missing Network offerings when creating new network [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Missing Network offerings when creating new network This sounds like a valid complaint. Physical network tags are useful for orchestration of zones/networks and should not be in the way. If you enter the “wrong” tag it could however

Re: QCOW2 on NFS shared storage

Hello guys, I will answer in this email to all the different responses I got. 1. Describe HA setup. * It’s a basic two-node HA cluster using ZFS. It is a TrueNAS F60 all-NVME. The network is using basic MLAG. The Linux hosts also have an MLAG as well. I understand this is not a network