fix: Use per-node shared flag for storage deduplication

The storage deduplication logic only checked cluster config's Shared
flag, but this required the cluster config API call to succeed. When
the per-node storage API already returns shared=1 (as the user
verified), we should use that directly.

Now we check three sources for shared storage detection:
1. Per-node API shared flag (storage.Shared)
2. Cluster config shared flag (if available)
3. Storage type heuristics (NFS, RBD, PBS, etc.)

Related to #1049
This commit is contained in:
rcourtman 2026-01-07 10:16:23 +00:00
parent dcdbee3c5c
commit 9cfcdbb247
18 changed files with 164 additions and 42 deletions

View file

@ -36,6 +36,12 @@ If a setting is disabled with an amber warning, it's being overridden by an envi
## 🔍 Monitoring & Metrics
### What is Pulse Pro, and what does it actually do?
Pulse Pro unlocks **AI Patrol** — scheduled, cross-system analysis that correlates real-time state, recent metrics history, and diagnostics to surface actionable findings.
Example output includes trend-based capacity warnings, backup regressions, and correlated container failures that simple threshold alerts miss.
See [AI Patrol](AI.md) and https://pulserelay.pro.
### Why do VMs show "-" for disk usage?
Proxmox API returns `0` for VM disk usage by default. You must install the **QEMU Guest Agent** inside the VM and enable it in Proxmox (VM → Options → QEMU Guest Agent).
See [VM Disk Monitoring](VM_DISK_MONITORING.md) for details.