From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 04 Nov 2003 - 23:00:28 GMT
On Tue, Nov 04, 2003 at 01:07:35PM +0100, Jan Zuchhold wrote:
> Hello list!
> There seems to be a problem with using nfs shares in a vserver with vs1.00.
> It appears that it is related to file locking.
> The share is mounted like this in the vserver startup script:
> /usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
> fileserver:/home /var/lib/vservers/$2/home
> After mounting the share it seems to work correctly (cd/ls/touch showing no
> When I start a process (in my case it's eclipse in jvm 1.4.1) which tries to
> lock a file on that nfs share, it goes to state D ('uninterruptible sleep')
> and cannot be killed. Any other process which tries to access the share goes
> to state D as well.
hmm, could you try to reproduce this without eclipse/jvm?
(some small C programm or perl script will do)
> Syslog on the Host says:
> Nov 4 11:57:04 galateia rpc.statd: Call to statd from non-local host
> Nov 4 11:57:04 galateia rpc.statd: STAT_FAIL to galateia for SM_MON of
> Nov 4 11:57:04 galateia kernel: lockd: cannot monitor 192.168.1.69
> Nov 4 11:57:05 galateia kernel: nfs: server fileserver not responding, still
> This problem does not appear in ctx-17c (the last version I tried before),
> although the first three syslog messages appear as well.
maybe the patch isn't the only variable in this game,
maybe you patched another (newer?) kernel with v1.00?
It is possible that v1.00 is the reason, but it is
unlikely, as the network code should be the same,
nevertheless I would appreciate further testing ...
so could you either provide kernel versions or do
some testing on your own, to narrow down this issue?
> Vserver mailing list
Vserver mailing list