| Re: Kind of a strange one: NFS [message #39087 is a reply to message #39079] |
Sun, 14 March 2010 03:41   |
VulcanRidr
Messages: 4 Registered: October 2009
|
Junior Member |
|
|
| maratrus wrote on Fri, 12 March 2010 12:34 | Hi,
| Quote: |
Can I use yorktown's large drive as an nfs store, not only for saratoga but for the entire network and still use it as an openvz HN?
|
Theoretically you can. But as I can see there are some problems with mounting yorktown's nfs share. It doesn't seem to be an OpenVZ issue. But if you feel like blaming OpenVZ don't hesitate to provide your arguments Search engine may help you to solve that problem.
|
I'm not prepared to blame OpenVZ at this point. I will say that it is something unique to yorktown as an nfs server. I set up a non-OpenVZ nfs server (lexington), and exported filesystems. I was able to not only able to mount from my workstation, which I set up as an nfs client, but from the saratoga, the openvz client.
For the record, I was also not able to mount from yorktown to my workstation either. Now, rpcinfo locally works on yorktown, showing programs for portmapper, status, nfs, nlockmgr and mountd. However, rpcinfo -p yorktown gives a permission denied. Of course, from rpcinfo -p lexington shows me the same ports/programs as a local rpcinfo would, which is expected behavior. I've checked firewall, tcpd, etc, and there is nothing between them.
I originally thought it might be something with the Debian OpenVZ kernel, but the nfs stuff was identical between linux-image-2.6.26-2-686 and linux-image-2.6.26-2-openvz-686:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y
| Quote: | | Quote: |
How many licks does it take to get to the center of a Tootsie Pop? (or am I showing my age with this one?
|
The world may never know. Is this the right answer?
|
Of course it is... 
|
|
|
|