VM /mnt Data Erroneously Landing on rpool

Benneffect

New Member
Mar 21, 2025
7
1
3
My PVE rpool has ghost data that I cannot remove.

I misconfigured VirtIOFS storage and somehow got rpool to contain my /mnt/vmdata rather than it being located on the intended storage pool, a 12TB RAIDZ pool (16TB raw). The storage was shared to my Ubuntu Server VM. Upon writing data (Immich, Nextcloud), my rpool filled up to over 100% and my VM stopped booting.

I've gone through troubleshooting, and I think I have properly set the storage location the the correct pool. But, I cannot delete the data that is accidentally in the rpool. I've deleted the data off the rpool, but it still shows as mostly full. And, when I start writing data to the VirtIOFS is still starts filling up again.

This is my first hypervisor & self-hosting project that I am slowly working on, so I am quite newb-ish in PVE / Ubuntu / Linux - I've been using round-robin help from AI, but they are not helping me solve my error. What files do I need to check to ensure my "/mnt/Data" is located on the right pool? How do I get the data off the rpool?

Here is what my VM sees:
ben@cloud357:/mnt$ tree -d
.
└── cloud357-data
├── immich-photos
├── personal-files [error opening dir]
└── template
└── cache

6 directories


Here is what the host has:
root@pve1:/mnt# tree -d
.
└── Data
└── cloud357-data
├── immich-photos
├── personal-files
│ └── nextcloud-data
└── template
└── cache
 
Hi, @Benneffect
Probably your intended pool wasn't mounted at /mnt
So the data landed on the "/" filesystem (which contains /mnt directory).

The fix is to umount whatever is mounted at /mnt (first shutdown VMs if they use this share).
Then inspect what really is inside /mnt

If /mnt contents is also in other secure place, you can delete the contents in /mnt
This should release "/" filesystem usage.