[PVE-User] Problems with backup process and NFS

Uwe Sauter uwe.sauter.de at gmail.com
Mon May 22 16:07:16 CEST 2017


Am 22.05.2017 um 15:40 schrieb Uwe Sauter:
> 
>>
>> I discovered a different issue with this definition: If I go to Datacenter -> node -> storage aurel -> content I only get "mount
>> error: mount.nfs: /mnt/pve/aurel is busy or already mounted (500)".
>>
>> The share is mounted again with IP address though I didn't change the config after above.
>>
>> # cat /proc/mounts
>> […]
>> <IP address>:/backup/proxmox-infra /mnt/pve/aurel nfs
>> rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=<IP
>> address>,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=<IP address> 0 0
>>
>> root at px-alpha-cluster:~# df
>> Filesystem                         1K-blocks      Used  Available Use% Mounted on
>> […]
>> <IP address>:/backup/proxmox-infra 4294967296  63842304 4231124992   2% /mnt/pve/aurel
>>
>>
>> Also Datacenter -> node -> storage aurel -> summary says:
>>
>> enabled: yes
>> active: no
>> content: vzdump backup file
>> type: NFS
>> usage: n/a
>>
>>
>> But to mention it again: backups do work now.
>>
> 
> The new issue is only true for the one node where no VM is running that has backups configured. The share is mounted but is not
> active and content is not shown (though the backups from VMs on other nodes should be visible).
> 

After some more testing it seems that this was some left-overs from previous configuration attempts. After a reboot, this issue
doesn't exist any more.


More information about the pve-user mailing list