Directory mounted on 2.5TB ZFS disk only uses 200GB
- Thread starter jsalas424
- Start date
I think this may be a related problem to another post I made: https://forum.proxmox.com/threads/what-is-suddenly-taking-up-so-much-space-on-local.78967/
This morning I woke up and found that my local storage had reached 100% and I was getting I/O errors. Interestingly, the size of the directory we're discussing is the size of my principle drive that completely locked up. Is this possible mounted/addressed wrong?
root@TracheServ:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 24G 0 24G 0% /dev
tmpfs 4.8G 9.5M 4.7G 1% /run
rpool/ROOT/pve-1 186G 104G 82G 56% /
tmpfs 24G 49M 24G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 24G 0 24G 0% /sys/fs/cgroup
/dev/sdc1 458G 276G 159G 64% /mnt/pve/spare
rpool 82G 128K 82G 1% /rpool
rpool/ROOT 82G 128K 82G 1% /rpool/ROOT
rpool/data 82G 128K 82G 1% /rpool/data
/dev/fuse 30M 24K 30M 1% /etc/pve
Storage.1 1.8G 128K 1.8G 1% /Storage.1
192.168.1.139:/data/backups/proxmox 870G 502G 369G 58% /mnt/pve/Proxmox_backups
tmpfs 4.8G 0 4.8G 0% /run/user/0
root@TracheServ:~# cat /etc/pve/storage.cfg
zfspool: local-zfs
pool rpool/data
content rootdir,images
sparse 1
dir: local
path /var/lib/vz
content rootdir,images,vztmpl,backup,snippets,iso
maxfiles 1
shared 0
zfspool: Storage.1
pool Storage.1
content images,rootdir
mountpoint /Storage.1
sparse 1
zfspool: Nextcloud.Storage
pool Nextcloud.Storage
content images,rootdir
mountpoint /Nextcloud.Storage
sparse 1
dir: spare
path /mnt/pve/spare
content backup,rootdir,vztmpl,snippets,iso,images
is_mountpoint 1
maxfiles 3
shared 1
nfs: Proxmox_backups
export /data/backups/proxmox
path /mnt/pve/Proxmox_backups
server 192.168.1.139
content rootdir,backup,images,vztmpl,iso,snippets
maxfiles 5
options vers=4.2
dir: User.data
path /Nextcloud.Storage
content images,vztmpl,snippets,iso,rootdir,backup
maxfiles 10
shared 1
root@TracheServ:~#
This morning I woke up and found that my local storage had reached 100% and I was getting I/O errors. Interestingly, the size of the directory we're discussing is the size of my principle drive that completely locked up. Is this possible mounted/addressed wrong?
root@TracheServ:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 24G 0 24G 0% /dev
tmpfs 4.8G 9.5M 4.7G 1% /run
rpool/ROOT/pve-1 186G 104G 82G 56% /
tmpfs 24G 49M 24G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 24G 0 24G 0% /sys/fs/cgroup
/dev/sdc1 458G 276G 159G 64% /mnt/pve/spare
rpool 82G 128K 82G 1% /rpool
rpool/ROOT 82G 128K 82G 1% /rpool/ROOT
rpool/data 82G 128K 82G 1% /rpool/data
/dev/fuse 30M 24K 30M 1% /etc/pve
Storage.1 1.8G 128K 1.8G 1% /Storage.1
192.168.1.139:/data/backups/proxmox 870G 502G 369G 58% /mnt/pve/Proxmox_backups
tmpfs 4.8G 0 4.8G 0% /run/user/0
root@TracheServ:~# cat /etc/pve/storage.cfg
zfspool: local-zfs
pool rpool/data
content rootdir,images
sparse 1
dir: local
path /var/lib/vz
content rootdir,images,vztmpl,backup,snippets,iso
maxfiles 1
shared 0
zfspool: Storage.1
pool Storage.1
content images,rootdir
mountpoint /Storage.1
sparse 1
zfspool: Nextcloud.Storage
pool Nextcloud.Storage
content images,rootdir
mountpoint /Nextcloud.Storage
sparse 1
dir: spare
path /mnt/pve/spare
content backup,rootdir,vztmpl,snippets,iso,images
is_mountpoint 1
maxfiles 3
shared 1
nfs: Proxmox_backups
export /data/backups/proxmox
path /mnt/pve/Proxmox_backups
server 192.168.1.139
content rootdir,backup,images,vztmpl,iso,snippets
maxfiles 5
options vers=4.2
dir: User.data
path /Nextcloud.Storage
content images,vztmpl,snippets,iso,rootdir,backup
maxfiles 10
shared 1
root@TracheServ:~#
Last edited: