Root filled after NAS went down

[masteroc]

I login one day to find that the root drive on my Proxmox server was filled. Upon investigation I found that the directory that I used to mount an NFS share on my NAS (/mnt/nfs) was not functioning since my NAS network interface had gone down.

What had seemingly happened was that a VM download client had continued to write to /mnt/nfs even after the server was down and had apparently just put the folders on the local media in a folder /mnt/nfs.

How can I configure the Proxmox box to not write to the local storage at all so that I don't end up with root full if my NAS goes down?

Thanks!

 

[RobFantini]

how did you set up the nfs client on proxmox?

for each type of virtual machine , how do you share the nfs to the clients?

 

[masteroc]

bind mount to Proxmox which had the NFS shares mounted on boot from /etc/fstab.

 

[RobFantini]

try not using /etc/fstab, and add storage using pve > storage.

 

[masteroc]

try not using /etc/fstab, and add storage using pve > storage.

The thing is that I don't want to use the NFS storage for ISO, Disk Image, etc..
It's only there to link to my NAS so that the containers can easily access it through a bind mount.
If I add the storage via pve > storage will my containers still be able to use for for Data storage?

Thanks

 

[Patrik Olsson]

Actually, how ever you mount a NFS resource, the directory, with or without the resource mounted, is treated like a normal directory. THi sis more a UNIX/NFS issue than a Promox. And famous last words, but I have not found a way to avoid this in my last 25 years as a Unix sysadmin But if someone has an idea, I stand corrected.

 

[RobFantini]

try this test:
1-at pve > storage , add the nfs . set it to be used for backups and templates. name it something like ' nfs-test '
2- backup a small vm or download a template to nfs-test
3- turn off the nfs
4- retry #2

using pve I have not seen writes to an unmounted nfs directory, however have not tested in a long time.