Linstor Cluster

Deploys the LINSTOR cluster via the Piraeus Operator to manage replicated block storage across Linux nodes.

  • Cloud
  • Infrastructure
  • Tools & Utilities
Deploys the LINSTOR cluster via the Piraeus Operator to manage replicated block storage across Linux nodes.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

8/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
251 install platform, install notes
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Checked 47 days ago - source: GitHub (piraeusdatastore/linstor-cluster)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Prepare storage and the LINSTOR database folder Create a dedicated disk pool (LVM thin pool) for storage, and create /var/lib/linstor with user/group ownership 1000:0. Without these, LINSTOR has no reliable place to store its database or data, and services can fail to start. source
  • Start the LINSTOR controller service Run systemctl enable --now linstor-controller on the host that runs it so the service starts now and again after reboot. If it is not running, the cluster cannot manage storage resources or respond to requests. source
  • Set up NFS if you use shared storage Install the NFS server (a shared-folder service), export a folder such as /export to your cluster nodes, and start the nfs-server service. Without that export, LINSTOR nodes cannot reach the shared secondary storage. source

Fetched 41 days ago - each note links to its source

Alternatives (1)

  • vSAN - vSAN is enterprise-class, storage virtualization software that, when combined with vSphere, allows you to manage compute and storage with a…

Checked 41 days ago - source: AlternativeTo

Common questions

What reasons do Proxmox users give for choosing LINSTOR as shared storage?

Users have selected LINSTOR for performance and redundancy in a Proxmox HA setup. The design keeps local storage for high-speed I/O while syncing it across nodes.

What happens if the linstor_db volume fails during a cold start?

If linstor_db does not come up, the primary node can become Diskless and other nodes can be Outdated. This can stop the controller and the cluster.

Which LINSTOR components were installed in a working Proxmox LINSTOR proof-of-concept?

A solved proof-of-concept for Proxmox 8.4.0 and LINSTOR 8.1.2 installed the LINSTOR common, controller, Proxmox, and satellite packages.

Answers sourced from forum.proxmox.com, forums.linbit.com, www.reddit.com

Community

Collected 48 days ago - public community threads