I had an issue where the local-lvm on a node was full.
I think it traced to an lvm-thin disk being the culprit.
I am only running Proxmox Backup Server in a VM on that node and didn't really care too much about losing anything on it (I had other backups).
I ended up getting impatient with trying various solutions to free up space and ended up using the Destroy option in the GUI.
I then added local-lvm back onto that node, however it is greyed out and not active.
Below is the output of some cli command that may help - I believe that the disk I want to use for local-lvm is sdb3
I really don't care too much whether I have to reformat that drive(s), or even reinstall the Proxmox Backup Server VM again, but just looking for the easiest solution. I'm a bit time poor at the moment and am not much of an advanced user.
Hoping someone can help out.
I think it traced to an lvm-thin disk being the culprit.
I am only running Proxmox Backup Server in a VM on that node and didn't really care too much about losing anything on it (I had other backups).
I ended up getting impatient with trying various solutions to free up space and ended up using the Destroy option in the GUI.
I then added local-lvm back onto that node, however it is greyed out and not active.
Below is the output of some cli command that may help - I believe that the disk I want to use for local-lvm is sdb3
Bash:
root@pve2:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
├─backup4tb-backup4tb_tmeta 252:2 0 15.9G 0 lvm
│ └─backup4tb-backup4tb-tpool 252:4 0 3.6T 0 lvm
│ └─backup4tb-backup4tb 252:5 0 3.6T 1 lvm
└─backup4tb-backup4tb_tdata 252:3 0 3.6T 0 lvm
└─backup4tb-backup4tb-tpool 252:4 0 3.6T 0 lvm
└─backup4tb-backup4tb 252:5 0 3.6T 1 lvm
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1007K 0 part
├─sdb2 8:18 0 1G 0 part /boot/efi
└─sdb3 8:19 0 1.8T 0 part
├─pve-swap 252:0 0 7.6G 0 lvm [SWAP]
└─pve-root 252:1 0 96G 0 lvm /
mmcblk0 179:0 0 29.1G 0 disk
├─mmcblk0p1 179:1 0 512M 0 part
├─mmcblk0p2 179:2 0 27.7G 0 part
└─mmcblk0p3 179:3 0 977M 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
Code:
root@pve2:~# pvesm status
pbs: error fetching datastores - 500 Can't connect to 192.168.50.234:8007 (No route to host)
no such logical volume pve/data
Name Type Status Total Used Available %
borg-backups cifs active 3905109820 3155288272 749821548 80.80%
local dir active 98497780 43884480 49563752 44.55%
local-lvm lvmthin inactive 0 0 0 0.00%
media-server-storage lvm disabled 0 0 0 N/A
pbs pbs inactive 0 0 0 0.00%
pve-shared nfs disabled 0 0 0 N/A
qnap-nas-backups nfs disabled 0 0 0 N/A
qnap-nas-public nfs disabled 0 0 0 N/A
Code:
root@pve2:~# pvesm scan lvm
pve
backup4tbI really don't care too much whether I have to reformat that drive(s), or even reinstall the Proxmox Backup Server VM again, but just looking for the easiest solution. I'm a bit time poor at the moment and am not much of an advanced user.
Hoping someone can help out.