From: Timm Essigke (essigke_at_eml.org)
Date: Tue 18 Feb 2003 - 14:15:14 GMT
Hi Matthieu,
I reported the same problem a couple of weeks ago, but didn't get it solved.
Matthieu Racine wrote:
> Hello,
>
> I've got the following problem :
>
> Main server :
>
> mount -t nfs nfssrv:/share/vserver1 /mnt/vserver1 => OK
> mount --bind /mnt/vserver1 /var/lib/vservers/vserver1/mnt/data => OK
>
> ls /mnt/vserver1 =>
> ls /var/lib/vservers/vserver1/mnt/data => OK
>
> vserver vserver1 enter
>
> ls /mnt/data
> ls: /mnt/data: Stale NFS file handle
It is the same for me. (Except, that I tried something like:
mount -t nfs nfssrv:/share/vserver1 /var/lib/vservers/vserver1/mnt/data)
>
>
> --------------------------
>
> What is running on Main server :
>
> as1:~# ps fax
> PID TTY STAT TIME COMMAND
> 1 ? S 0:05 init [2]
> 2 ? SW 0:00 [keventd]
> 3 ? SWN 0:00 [ksoftirqd_CPU0]
> 4 ? SW 0:00 [kswapd]
> 5 ? SW 0:00 [bdflush]
> 6 ? SW 0:00 [kupdated]
> 7 ? SW 0:00 [kjournald]
> 73 ? SW 0:00 [kjournald]
> 74 ? SW 0:00 [kjournald]
> 75 ? SW 0:00 [kjournald]
> 76 ? SW 0:00 [kjournald]
> 77 ? SW 0:00 [kjournald]
> 95 ? SW 0:00 [eth0]
> 100 ? S 0:00 /sbin/portmap
> 156 ? S 0:00 /sbin/syslogd
> 159 ? S 0:00 /sbin/klogd
> 163 ? S 0:00 /sbin/rpc.statd
> 168 ? S 0:00 /usr/sbin/inetd
> 172 ? S 0:00 /usr/sbin/nullmailer-send
> 175 ? S 0:00 /usr/sbin/rebootmgr --pidfile
> /var/run/rebootmgr.pid vserver1
> 183 ? S 0:00 /usr/sbin/sshd
> 13898 ? R 0:00 \_ /usr/sbin/sshd
> 13900 pts/1 S 0:00 \_ -bash
> 13926 pts/1 R 0:00 \_ ps fax
> 259 ? S 0:00 /usr/sbin/atd
> 262 ? S 0:00 /usr/sbin/cron
> 265 tty1 S 0:00 /sbin/getty 38400 tty1
> 266 tty2 S 0:00 /sbin/getty 38400 tty2
> 267 tty3 S 0:00 /sbin/getty 38400 tty3
> 268 tty4 S 0:00 /sbin/getty 38400 tty4
> 269 tty5 S 0:00 /sbin/getty 38400 tty5
> 270 tty6 S 0:00 /sbin/getty 38400 tty6
> 13873 ? SW 0:00 [rpciod]
> 13874 ? SW 0:00 [lockd]
>
> ------------------------------------
>
> What is running on vserver1
>
> vserver1:/# ps fax
> PID TTY STAT TIME COMMAND
> 13968 pts/1 S 0:00 /bin/bash -login
> 13977 pts/1 R 0:00 \_ ps fax
> 1 ? S 0:05 init [2]
> 11941 ? S 0:00 /sbin/syslogd
> 11955 ? S 0:00 /usr/sbin/sshd
> 12364 ? S 0:00 /usr/sbin/cron
> 12559 ? S 0:00 /usr/sbin/apache
> 13652 ? S 0:00 \_ /usr/sbin/apache
> 13653 ? S 0:00 \_ /usr/sbin/apache
> 13654 ? S 0:00 \_ /usr/sbin/apache
> 13655 ? S 0:00 \_ /usr/sbin/apache
> 13656 ? S 0:00 \_ /usr/sbin/apache
> 13762 ? S 0:00 \_ /usr/sbin/apache
>
> ----------
>
> kernel version 2.4.19-ctx-15
I heard, that it worked in 2.4.19-ctx14, but I haven't verified myself,
because I need at least 2.4.20 for my machine. 2.4.20 and 2.4.21-pre4
have the same problem...
>
>
> The vserver has no capabilities set.
> From the vserver, I can ssh to nfs.
>
> I supose that I'm not running all the necessary on the vserver but I
> cannot run portmap nor rpc.*
> because they are bound to 0.0.0.0 on the main server and I don't know
> how to bind them only on specifics IPs.
You can use a wrapper script as for e.g. apache as distributed with
vserver to bind your portmap etc. to your host-ip (check with netstat
-ap). But it didn't help for me...
>
>
> Even then, I'm afraid that they could overlap each others and cause
> data corruption on the nfs server ???
I am not sure if you need the portmapper in your vserver, because it is
neither nfs-client nor nfs-server. This should be handled by the host
system AFAIK.
>
>
> If anyone has any idea, it would be great....
Maybe try to downgrade to ctx14 and let me know if this works (just for
interest).
>
>
> Thanks,
> --
> Matthieu
>
> PS : Sorry for my poor English...
>
>
Sorry, I guess I am not a big help!
Timm