OpenVZ Forum: Support » nfs caching/delay from within a container

Home » General » Support » nfs caching/delay from within a container

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: nfs caching/delay from within a container [message #36038 is a reply to message #35320]

Wed, 13 May 2009 15:03

kclair
Messages: 2
Registered: March 2009

Junior Member

we updated our kernel and are now using 2.6.18-92.1.18.el5.028stab060.8ent. however, the problem persists.

i do notice a lot of rpc.statd and lockd errors, such as the following:

rpc.statd[6462]: STAT_FAIL to www-vps for SM_MON of 192.168.0.4
kernel: lockd: cannot monitor 192.168.0.4

when this occurs, the problem is seen both from within the vps and from the openvz host server (the nfs filesystems are mounted with --bind in the vps). oddly, doing an ls -l of the directory where the problem is happening seems to jolt the server into reality, "fixing" the problem.

i definitely acknowledge that this could be a problem unrelated to openvz, but our openvz servers are our only servers with this problem.

is anyone else using nfs with openvz in a high-use environment where the main data (in this case website files) is stored on nfs?

thanks!

Report message to a moderator

[Message index]

		nfs caching/delay from within a container By: kclair on Tue, 17 March 2009 13:47
		Re: nfs caching/delay from within a container By: maratrus on Wed, 18 March 2009 17:27
		Re: nfs caching/delay from within a container By: kclair on Wed, 13 May 2009 15:03
		Re: nfs caching/delay from within a container By: abulava on Thu, 14 May 2009 13:24

Previous Topic:	port forwarding (http servers on each VPS)
Next Topic:	Error in Quick Installation instructions?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Jul 28 22:39:27 GMT 2025

Total time taken to generate the page: 0.56766 seconds