directories issues with 100gb limit and random occupation

vicesig

New Member
Jul 10, 2023
4
0
1
Hello!
i have a proxmox installation on a server.
In this server, i have put some linked folders and some storages as following:
linked:
- local network drive mounted on another PC (500gb)
- onedrive with 2tb
local:
- 1 SSD 1TB
- 7 HDD 1TB (i made a ZFS pool)
- 1 SDcard (512gb)

the issue is, all the drives/linked folders that I have put as directories show an incorrect size and they tend to become full. They all show the same space occupied, around the 85gb mark, and the total size as 100gb. This is indipendent from the backup usage (some are used for backups, some don't).

This tend to lock up the server backups. What am I missing? i searched around but I haven't found anyone with this kind of behaviour. Running 7.4-16, some screenshots attached
 

Attachments

  • firefox_6qFsspjME8.png
    firefox_6qFsspjME8.png
    38.7 KB · Views: 8
  • firefox_8hhuop1ZYp.png
    firefox_8hhuop1ZYp.png
    31.1 KB · Views: 8
  • firefox_JryhUz9Yec.png
    firefox_JryhUz9Yec.png
    7.8 KB · Views: 9
  • firefox_KJfXvBZ80s.png
    firefox_KJfXvBZ80s.png
    20.8 KB · Views: 9
  • firefox_mjBMPg2Qfy.png
    firefox_mjBMPg2Qfy.png
    40.3 KB · Views: 8
  • firefox_QnefHtv3T4.png
    firefox_QnefHtv3T4.png
    47.8 KB · Views: 7
  • firefox_RnzEHv26r5.png
    firefox_RnzEHv26r5.png
    36.7 KB · Views: 6
  • firefox_SwTkAELSuH.png
    firefox_SwTkAELSuH.png
    37.3 KB · Views: 8
You need to make sure that the directories below /mnt are mounted before the Proxmox services start.

We do this by adding these options to their /etc/fstab entries: _netdev,x-systemd.after=remote-fs-pre.target,x-systemd.before=remote-fs.target
 
i'm sorry but I have a smooth brain..
this is my fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
 
in any case you should also mark those directories as mountpoints ("is_mountpoint" in storage.cfg) so that PVE knows it should not treat them as active if nothing is mounted there..
 
  • Like
Reactions: gurubert