I have a problem adding a second OVH MININAS to Proxmox storage as VZdump Backup

R

raid

Member
Jul 25, 2010
102
0
16
Italy
Hi,
I had a mini NAS mounted on my Proxmox 1.7 and used for VZdumpbackup.
This morning I added a second NAS (the idea is using a NAS for each VM), I follow the instruction as usual but I get an error adding the the new NAS to the Proxmaox storage via web page.
I deleted the new storage to start again, but the old NAS too disappeared.
The dir /BACKUP is again there, but on the storage screen I see only the local storage.
When I try to add it again I get the following error: mkdir /mnt/pve/BACKUP: No space left on device at /usr/share/perl5/PVE/Storage.pm line 2141.

Any tips on how to solve this problem and on how to add the second NAS?
Thanks in advance
Luc

P.S.: I use Proxmox 1.7
root@ns:~# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
10.16.101.6:/nas-000127/mininas-000145 on /BACKUP type nfs (rw,addr=10.16.101.6)
10.16.101.6:/nas-000127/mininas-000145/ on /mnt/pve/ProxMox-BK type nfs (rw,addr=10.16.101.6)
10.16.101.3:/nas-000009/mininas-001293 on /BACKUP-Plesk type nfs (rw,addr=10.16.101.3)
--------------------
root@ns:~# vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3354
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 921.00 GB
PE Size 4.00 MB
Total PE 235777
Alloc PE / Size 210202 / 821.10 GB
Free PE / Size 25575 / 99.90 GB
VG UUID dbByVK-e5ZD-t1TS-j4hk-4UxV-qlHK-9ArUMB
/etc/lvm/cache/.cache.tmp: write error failed: No space left on device
 
root@ns:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 10403128 10403128 0 100% /
tmpfs 4112132 0 4112132 0% /lib/init/rw
udev 10240 552 9688 6% /dev
tmpfs 4112132 0 4112132 0% /dev/shm
/dev/mapper/pve-data 854098692 53025200 758029452 7% /var/lib/vz
10.16.101.6:/nas-000127/mininas-000145
104857600 75264000 29593600 72% /BACKUP
10.16.101.6:/nas-000127/mininas-000145/
104857600 75264000 29593600 72% /mnt/pve/ProxMox-BK
10.16.101.3:/nas-000009/mininas-001293
104857600 7937024 96920576 8% /BACKUP-Plesk
root@ns:/#

-----------------
[TABLE="class: normal, width: 100%"]
[TR]
[TH="colspan: 1"][/TH]
[TH="colspan: 1"]Nome Storage[/TH]
[TH="colspan: 1"]Tipo[/TH]
[TH="colspan: 1"]Abilitato[/TH]
[TH="colspan: 1"]Attivo[/TH]
[TH="colspan: 1"]Condiivso[/TH]
[TH="colspan: 1"]Utilizzato (GB)[/TH]
[TH="colspan: 1"]Capacità (GB)[/TH]
[TH="colspan: 1"] [/TH]
[/TR]
[TR="class: link, bgcolor: #EDEDED"]
[TD]
tarrdown.png
[/TD]
[TD]local[/TD]
[TD]Directory[/TD]
[TD]Sì[/TD]
[TD]Sì[/TD]
[TD]No[/TD]
[TD]50.57[/TD]
[TD]773.48[/TD]
[/TR]
[/TABLE]
 
I suppose something is gone wrong adding the second MiniNAS, but I can't figure what :-(
Could you suggest any Post on the argument?
Thanks
 
Update: any proxmox developer could tell me anything about this?
root@ns:/# du -sh
du: cannot access `./proc/22669/task/22669/fd/4': No such file or directory
du: cannot access `./proc/22669/task/22669/fdinfo/4': No such file or directory
du: cannot access `./proc/22669/fd/4': No such file or directory
du: cannot access `./proc/22669/fdinfo/4': No such file or directory
du: cannot access `./proc/22677': No such file or directory
du: cannot access `./proc/22678': No such file or directory
du: cannot access `./proc/22679': No such file or directory
470G .
-------------
I cannot install ncdu "no free space"

root@ns:/# du -xhs /*
40G /BACKUP
1.1G /BACKUP-LOCALE
32G /BACKUP-Plesk
5.0M /bin
23M /boot
552K /dev
8.8M /emul
6.5M /etc
4.0K /home
127M /lib
0 /lib32
0 /lib64
16K /lost+found
4.0K /media
23K /mnt
4.0K /opt
du: cannot access `/proc/29652/task/29652/fd/4': No such file or directory
du: cannot access `/proc/29652/task/29652/fdinfo/4': No such file or directory
du: cannot access `/proc/29652/fd/4': No such file or directory
du: cannot access `/proc/29652/fdinfo/4': No such file or directory
0 /proc
260K /root
11M /sbin
4.0K /selinux
4.0K /srv
0 /sys
24K /tmp
504M /usr
310M /var
0 /vz
----------------------------------
du -hxs /
2.0G /
-----------------------------------
 
Last edited:
I deleted some files and I free 1GB on /, later I have succesfully added the 2 storages and setted the backup.

Still I cannot figure out what is using my empty disk space.

Also, I mounted the 2 NAS in 2 dirs "/BACKUP" and "/BACKUP-Plesk" but I see them also mounted in "/mnt/pve/ProxMox-BK" and "/mnt/pve/BK-102", ProxMox-BK and BK-102 are the names of the storages, where is my mistake? Why I have 2 duplicated mounting points?

steps:
1) mkdir "/BACKUP-Plesk",
2) mount -tnfs 10.16.101.3:/nas-000009/mininas-001293 /BACKUP-Plesk/
3) added to fstabs: 10.16.101.3: /nas-000009/mininas-001293 /BACKUP-Plesk nfs default 0 0
3) added the storage to the Proxmox GUI using "BK-102" as storage name
4) set Backup

thanks anyone for help
 
raid said:
but I see them also mounted in "/mnt/pve/ProxMox-BK" and "/mnt/pve/BK-102", ProxMox-BK and BK-102 are the names of the storages, where is my mistake? Why I have 2 duplicated mounting points?
Click to expand...

PVE itself uses those mount points.

I suggest you unmount /BACKUP and /BACKUP-Plesk.

Please check if there is any data in those directories after unmounting (also check with /mnt/pve/ProxMox-BK and /mnt/pve/BK-102).
 
  • Like
Reactions: 1 person
dietmar said:
PVE itself uses those mount points.
I suggest you unmount /BACKUP and /BACKUP-Plesk.
Please check if there is any data in those directories after unmounting (also check with /mnt/pve/ProxMox-BK and /mnt/pve/BK-102).
Click to expand...

This solved!

root@ns:~# df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 10G 1.2G 8.4G 12% /

Thank you Dietmar
 
You must log in or register to reply here.
Top Bottom