10 Things You Can Do With LINSTOR & Proxmox

[@redetermine]

Seems like a great product, I will definitely keep you in mind as our business continues to scale!

[@Glatze603]

That‘s really interesting! Thanks a lot.

[@GrishTech]

This is fantatic. Have you guys considered having proxmox add this into their storage types and be available, along with Ceph for the other type of workloads. Most workloads just need a simple replica, where ceph is just overkill.

[@linbit]

Thanks for your suggestion - will pass to the team 🤔

[@omgnowairly]

This is solid.

[@yamanalsayed5858]

Nice *hit !!

[@jmhcxh]

I encountered a problem during testing. I have 2 nodes and a diskless node. It seems that there is a problem with the quorum. When one of my storage nodes fails, the entire storage cannot work. Please tell me what to do

[@rycodge]

It sounds like you most likely need to make the LINSTOR Controller highly available. If you're losing the control plane when your storage node fails, Proxmox can no longer tell LINSTOR what to do with the storage when you perform new actions such as start a VM, or allocate new storage, etc. 1) Make the LINSTOR Controller highly available. 2) Add each possible controller IP address (should be your two storage nodes) to the PVE storage configuration for LINSTOR. I would link the url's for sections of our LINSTOR User's Guide, but I think my previous comment got flagged for doing do. A quick google search for the LINSTOR User's Guide should get you to the information needed to do steps 1 & 2 above.

[@jmhcxh]

@@rycodge Thank you very much, but that's not how it works. I have two storage nodes and a diskless node. I installed the controller on the diskless node. When I shut down a storage node, the pve storage and vm became unavailable. I don't know what I did wrong. Are there parameters that need to be specially adjusted?

[@rycodge]

@@jmhcxh Hmm, do you actually have a "three node" cluster configured in Proxmox? For HA you'll need to setup a qdevice on the quorum node. If you power down one storage host, do VMs (backed by LINSTOR) continue to run on the other node?

[@jmhcxh]

​@@rycodgeIt's because linstor lost a storage node and the remaining storage cannot be read or written. It's not a problem with the pve platform.

[@rycodge]

@@jmhcxh 'linstor resource list' and 'drbdadm status' (run from each node) will inform you of the current status of each replicated resource in the cluster. The status of the resources would point you in the direction to take action. There's a number of things that could be causing this, for example a quorum node that cannot reach one of the storage nodes (in the replication/DRBD network for quorum), that would cause the remaining LINSTOR node to lose quorum for any resources that were active on the node that was down, and refuse to do anything until the other "diskfull" node is powered back up.