NFS mount on a CT

[informant]

Hi, we would mount a storage on a ct. this ct have installed debian wheezy.
the node have 2 network cards. one for internet and one for intranet to storage.
we have add a 2nd nertwork vbmr1 (intranet) to eth0 on this ct.
we can ping the intranet ip´s but not the storage ip.
the host-server can ping the storage.

We do this:

stop ct

vzctl set 101 --features "nfs:on" --save

start ct

than:

ssh: mount -t nfs 10.11.12.50:/volume1/storage /mnt/backup/
mount: wrong fs type, bad option, bad superblock on 10.11.12.50:/volume1/storage,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

than:

aptitude install nfs-utils nfs-utils-lib
packages not found

???

than:

aptitude install rpcbind

than:

aptitude install nfs-common

than i would mount, its comes no result. what can i do? please help.

regards

---

 

[mir]

Try:
mount -t nfs -o vers=3 10.11.12.50:/volume1/storage /mnt/backup

Reason: nfsv4 is not supported in CT's

 

[informant]

hi mir,

thanks for answer.
we get the same issue. after mount command its comes not result.

i can´t ping the ip of the storage out of the ct, only from the host-server. other intranet ips i can ping normal. after a long time it comes: mount.nfs: Connection timed out

traceroute 10.11.12.50
traceroute to 10.11.12.50 (10.11.12.50), 30 hops max, 60 byte packets
 1  s1.domain.de (217.69.254.65)  0.042 ms  0.011 ms  0.011 ms
 2  10.11.12.50 (10.11.12.50)  0.284 ms  0.352 ms  0.424 ms
ping 10.11.12.50
PING 10.11.12.50 (10.11.12.50) 56(84) bytes of data.
^C
--- 10.11.12.50 ping statistics ---
109 packets transmitted, 0 received, 100% packet loss, time 108001ms

any ideas?

regards

 

[mir]

What does the following commands show when executed inside the CT:
route -n
rpcinfo 10.11.12.50
Are there any firewalls involved (host, storage)?

 

[informant]

route -n
Kernel-IP-Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 venet0

and

rpcinfo 10.11.12.50
   program version netid     address                service    owner
    100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser
    100003    2    tcp       0.0.0.0.8.1            nfs        superuser
    100003    3    tcp       0.0.0.0.8.1            nfs        superuser
    100003    4    tcp       0.0.0.0.8.1            nfs        superuser
    100003    2    udp       0.0.0.0.8.1            nfs        superuser
    100003    3    udp       0.0.0.0.8.1            nfs        superuser
    100003    4    udp       0.0.0.0.8.1            nfs        superuser
    100021    1    udp       0.0.0.0.217.11         nlockmgr   superuser
    100021    3    udp       0.0.0.0.217.11         nlockmgr   superuser
    100021    4    udp       0.0.0.0.217.11         nlockmgr   superuser
    100021    1    tcp       0.0.0.0.226.88         nlockmgr   superuser
    100021    3    tcp       0.0.0.0.226.88         nlockmgr   superuser
    100021    4    tcp       0.0.0.0.226.88         nlockmgr   superuser
    100021    1    udp6      ::.221.27              nlockmgr   superuser
    100021    3    udp6      ::.221.27              nlockmgr   superuser
    100021    4    udp6      ::.221.27              nlockmgr   superuser
    100021    1    tcp6      ::.186.150             nlockmgr   superuser
    100021    3    tcp6      ::.186.150             nlockmgr   superuser
    100021    4    tcp6      ::.186.150             nlockmgr   superuser
    100005    1    udp       0.0.0.0.3.124          mountd     superuser
    100005    1    tcp       0.0.0.0.3.124          mountd     superuser
    100005    2    udp       0.0.0.0.3.124          mountd     superuser
    100005    2    tcp       0.0.0.0.3.124          mountd     superuser
    100005    3    udp       0.0.0.0.3.124          mountd     superuser
    100005    3    tcp       0.0.0.0.3.124          mountd     superuser
    100024    1    udp       0.0.0.0.193.240        status     superuser
    100024    1    tcp       0.0.0.0.166.175        status     superuser

we dont have firewals. in storage i have the nfs share right with * permissions. accept for all.

i dont understand, why i can´t ping the storage out of ct, but from hostserver. out of ct i can ping the intranet ip of many devices and the intranet ip of the host-server´s. but not the ip of storage.

regards

 

[mir]

could you try adding a veth instead of a venet to the CT?
I think to remember that there are some limitations to venet.

 

[informant]

hi mir,

i have add already a veth. show screenshot:



do you have any ideas or do you have time for a teamviewer session?

regads

 

[mir]

hi mir,

i have add already a veth. show screenshot:

View attachment 1415

do you have any ideas or do you have time for a teamviewer session?

regads

But you have not assigned any IP to hvis Vieth in the CT.

 

[informant]

how can i set this in veth? in venet i can set. in veth only a bridge.

regards

 

[mir]

You should remove your venet and only use the veth.

If your CT is using Debian as distribution this is how you do it:
1) login as root
2) nano /etc/network/interfaces
3) add the following (< and > is to be removed also):
auto eth0
iface eth0 inet static
address <IP>
netmask <netmask for net>
network <IP for network>
gateway <default gateway for net>
4) save file
5) reboot

 

[tom]

..

do you have any ideas or do you have time for a teamviewer session?

regads

This is a community forum,pls do not request direct remote help from community members here. If you use Proxmox VE in a production environment and you need help, consider a support subscription.

 

[informant]

Hi, i do need also 2 venets, well we have a internet ip adress and a intranet ip, right? well without internet ip the server is not reachable.

After create a venet and manualle entry in interfaces + restart, ping said: network is unreachable.

regards

 

[informant]

Hi,

i have deleted all network entries and create first the intranet venet and than the internet venet. than its works fine. first internet and than intranet doesn´t work. it´s a bug i think. both networks parallel doens´t work

regards and very thanks for help.