/dev/mapper/pve-root 90% full
- Thread starter skylowe
- Start date
You were right.
BUT ncdu -x did not show the offending directory.
On a hunch I unmounted my zfs pool only to find 50gb direectory in the zfs pool mount directory. Must have been written when the pool was unmounted.
So my question is - how do you prevent writting happening to this zfs mountpoint when the zfs pool is not mounted?
BUT ncdu -x did not show the offending directory.
On a hunch I unmounted my zfs pool only to find 50gb direectory in the zfs pool mount directory. Must have been written when the pool was unmounted.
So my question is - how do you prevent writting happening to this zfs mountpoint when the zfs pool is not mounted?
I'm also interested in this. Some days ago someone posted that the root partition was full. The problem was that Proxmox started a backup to a not mounted external USB-HDDs so everything was written to the root LV instead of the USB-HDD.
Is there maybe a way using LVM/ZFS to forbid writes to a mountpoint that isn't mounted or to set some kind of quota?
I thought about setting up chmod 700 with root as owner for the mountpoint and something like chmod 750 owned by a unprivileged user for the mounted drive/share so it can't be written if not mounted properly. But if I understand it right, that wouldn't work for backups for example, because the backup process is run by root and can ignore any rights limitations.
And I also thought about some kind of quota. So that the unmounted mountpoint may only store like 1MB of data but I don't know if it would be possible to overwrite that quota when the mointpoint gets mounted.
Last edited:
I am mounting nfs in my VMs via /etc/fstab with using systemd units/syntax. When the storage is not available, system block access into mountpoint. https://wiki.archlinux.org/title/fstab#Automount_with_systemd
