Kind of a strange one: NFS [message #39044] |
Sat, 06 March 2010 16:28 |
VulcanRidr
Messages: 4 Registered: October 2009
|
Junior Member |
|
|
I have a few servers at home. On two of them I am running OpenVZ, a Dell 2550 and an IBM something or other that came my way.
Well, I just bought an HP DL360, which I *thought* was 64 bit, enabling me to run Proxmox, and therefore OpenVZ _and_ KVM. Alas, it was 32 bit, so I am making the best of a bad situation.
So the IBM box, named yorktown, is my current primary OpenVZ server, since it was the fastest server in my network until I got the HP box (named saratoga). My goal here is to retire prometheus, the Dell 2550.
Okay. So, we have saratoga, yorktown and prometheus, all running Debian testing, all running vzctl version 3.0.23 and all running the kernel 2.6.26-2-openvz-686. prometheus has a RAID-5 array of 5 73GB SCSI drives. yorktown is SATA-capable, and has an 80GB and a 1.5TB drive. (I had intended on doubling up as an OpenVZ HN and an NFS server (hence the NFS server portion of the topic)). saratoga has a pair of 73GB SCSI drives...Which, while insufficient for my needs, was something I was willing to sacrifice for the 64bit VTX capable processor...I got screwed coming and going on that one.
So, I was planning to make saratoga my replacement OpenVZ server, but I would have to remotely mount the CTs from a different machine -- yorktown.
I played with it briefly last night, but couldn't get it to work. I was getting the following error:
# mount yorktown:/media/vz /mnt
mount.nfs: mount to NFS server 'yorktown:/media/vz' failed: RPC Error: Unable to receive; errno = Connection refused
Unfortunately, I am completely new to NFS as well, because earlier versions had...issues. I have also been a security engineer as well as a sysadmin, so NFS was something to be avoided, "No F%^&@* Security"...
So here are my questions:
- 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?
- Can I mount saratoga's drives from somewhere (ideally yorktown) and use the CTs on an nfs mounted partition?
- How many licks does it take to get to the center of a Tootsie Pop? (or am I showing my age with this one? )
Thanks,
--vr
|
|
|
|
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...
|
|
|
Re: Kind of a strange one: NFS [message #39114 is a reply to message #39087] |
Tue, 16 March 2010 16:52 |
maratrus
Messages: 1495 Registered: August 2007 Location: Moscow
|
Senior Member |
|
|
Hi,
i tried 2.6.26-dostoevsky.1 kernel and everything works like clockwork.
The only steps I did are the following
# sudo /etc/init.d/nfslock restart
audit_log_user_command(): Connection refused
Stopping NFS statd: [ OK ]
Starting NFS statd: [ OK ]
# sudo /etc/init.d/nfsrestart
sudo: /etc/init.d/nfsrestart: command not found
# sudo /etc/init.d/nfs restart
audit_log_user_command(): Connection refused
Shutting down NFS mountd: [FAILED]
Shutting down NFS daemon: [FAILED]
Shutting down NFS services: [FAILED]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
# uname -a
Linux myhost 2.6.26-dostoevsky.1 #1 SMP Fri Apr 3 19:08:02 MSD 2009 i686 i686 i386 GNU/Linux
# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 684 status
100024 1 tcp 687 status
100011 1 udp 753 rquotad
100011 2 udp 753 rquotad
100011 1 tcp 756 rquotad
100011 2 tcp 756 rquotad
100021 1 udp 54911 nlockmgr
100021 3 udp 54911 nlockmgr
100021 4 udp 54911 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 tcp 51973 nlockmgr
100021 3 tcp 51973 nlockmgr
100021 4 tcp 51973 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 795 mountd
100005 1 tcp 798 mountd
100005 2 udp 795 mountd
100005 2 tcp 798 mountd
100005 3 udp 795 mountd
100005 3 tcp 798 mountd
# cat /etc/exports
/vz/private/102/ *(rw,no_root_squash,nohide,no_subtree_check)
# service vz status
OpenVZ is running...
from another computer
# sudo mount -t nfs myhost:/vz/private/102 /mnt/
# echo $?
0
|
|
|