mounting NAS on CentOS 6.1

NikolaPiterskiy

New Member
Hi all,
I could not mount any points on NAS (Supermicro under RH) from client workstation under CentOS 6.1 or from another workstation under LinuxMint 19.....
Actually i have access to NAS via ssh... from both workstations... but i need normal mounted point...

I have tried from both workstations mount chinchilla:/raid1/ARGUS /mnt/datanas
mount -t nfs chinchilla:/raid1/ARGUS /mnt/datanas
mount.nfs chinchilla:/raid1/ARGUS /mnt/datanas
mount /mnt/datanas (after fstab entry like "chinchilla:/raid1/ARGUS /mnt/datanas nfs bg,hard 0 0")
mount -o udp chinchilla:/raid1/ARGUS /mnt/datanas
No any positive result... just looks like something in progress but nothing going on

exports file on NAS machines looks like: "/raid1/ARGUS *(ro,async,nohide,root_squash,mp=/raid1) svr428(rw,sync,all_squash,anonuid=40647,anongid=100,nohide,mp=/raid1) jaguar(rw,sync,no_root_squash,no_subtree_check,mp=/raid1)"

Any ideas about it?
 


NikolaPiterskiy

New Member
Hey there, welcome to the forum!

Couple obvious questions.. what do you get if you ping chinchilla? Also, you aren't seeing any error messages at all when doing these commands?
Hi,
Thanks for answer
I can ping it from any ends, ping from chinchilla to jaguar - OK and ping from jaguar to chinchill - OK...
After typing any mount command - no any messages

[[email protected] DataNas]# mount -t nfs chinchilla:/raid1/ARGUs /mnt/datanas
^C
[[email protected] DataNas]# mount /mnt/datanas
^C
I just go of (by Cntrl+C) after couple minutes cause going on nothing
 

NikolaPiterskiy

New Member
PING chinchilla (172.27.128.41) 56(84) bytes of data.
64 bytes from chinchilla (172.27.128.41): icmp_seq=1 ttl=64 time=0.257 ms
64 bytes from chinchilla (172.27.128.41): icmp_seq=2 ttl=64 time=0.227 ms
64 bytes from chinchilla (172.27.128.41): icmp_seq=3 ttl=64 time=0.259 ms
^C
--- chinchilla ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2055ms
rtt min/avg/max/mdev = 0.227/0.247/0.259/0.023 ms
 

Rob

Administrator
Staff member
I'd let it error out and see what you can get from it. See if it times out or whatever. Also, maybe look in /var/log/messages to see if there's any hints.. maybe even typing dmesg to see if there's anything
 

NikolaPiterskiy

New Member
I'd let it error out and see what you can get from it. See if it times out or whatever. Also, maybe look in /var/log/messages to see if there's any hints.. maybe even typing dmesg to see if there's anything
Oh thanks

dmesg output:

NFS: Registering the id_resolver key type
Key type id_resolver registered
FS-Cache: Netfs 'nfs' registered for caching
nfs: server 172.27.128.41 not responding, still trying
Installing knfsd
(copyright (C) 1996 [email protected]).
SELinux: initialized (dev nfsd, type nfsd), uses genfs_contexts
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
nfs: server 172.27.128.41 not responding, still trying
nfs: server chinchilla not responding, still trying
nfs: server chinchilla not responding, still trying
Netfilter messages via NETLINK v0.30.
ip_set: protocol 6
nfs: server chinchilla not responding, still trying
nfs: server chinchilla not responding, still trying
 

dos2unix

Active Member
My first thought thought here is... either your nfs server, or your nfs client isn't installed.

Can you show the output of "yum list installed | grep nfs".

service nfs status
service rpcbind status

Another possibility is your firewall is blocking the nfs port.
Are ports 111 and 2049 open? tcp/udp
 

NikolaPiterskiy

New Member
My first thought thought here is... either your nfs server, or your nfs client isn't installed.

Can you show the output of "yum list installed | grep nfs".

service nfs status
service rpcbind status

Another possibility is your firewall is blocking the nfs port.
Are ports 111 and 2049 open? tcp/udp
On NAS:
yum list installed:
nfs-utils.x86_64 1:1.0.9-66.el5 installed
nfs-utils-lib.x86_64 1.0.8-7.9.el5 installed
system-config-nfs.noarch 1.3.23-2.el5 installed

On client:
nfs-utils.x86_64 1:1.2.3-78.el6_10.1 @updates
nfs-utils-lib.x86_64 1.1.5-13.el6 @base
nfs4-acl-tools.x86_64 0.3.3-8.el6 @base


[[email protected] raid1]# service nfs status
rpc.mountd (pid 3644) is running...
nfsd (pid 3641 3640 3639 3638 3637 3636 3635 3634) is running...
rpc.rquotad (pid 3628) is running...

And ups:...
[[email protected] raid1]# service rpcbind status
rpcbind is stopped
 

NikolaPiterskiy

New Member
[[email protected] sbin]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 770 status
100024 1 tcp 773 status
100011 1 udp 837 rquotad
100011 2 udp 837 rquotad
100011 1 tcp 840 rquotad
100011 2 tcp 840 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 54157 nlockmgr
100021 3 udp 54157 nlockmgr
100021 4 udp 54157 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 53767 nlockmgr
100021 3 tcp 53767 nlockmgr
100021 4 tcp 53767 nlockmgr
100005 1 udp 852 mountd
100005 1 tcp 855 mountd
100005 2 udp 852 mountd
100005 2 tcp 855 mountd
100005 3 udp 852 mountd
100005 3 tcp 855 mountd
 

NikolaPiterskiy

New Member
SOLVED:
etc/hosts.allow On SERVER:
portmap: 10.111.0.0/255.255.255.0 , 172.27.0.0/255.255.255.0
lockd: 10.111.0.0/255.255.255.0 , 172.27.0.0/255.255.255.0
rquotad: 10.111.0.0/255.255.255.0 , 172.27.0.0/255.255.255.0
mountd: 10.111.0.0/255.255.255.0 , 172.27.0.0/255.255.255.0
statd: 10.111.0.0/255.255.255.0 , 172.27.0.0/255.255.255.0

etc/hosts.deny
blank

etc/exports
/raid1/ARGUS *(rw,async,nohide,root_squash,mp=/raid1)
instead:
/raid1/ARGUS *(ro,async,nohide,mp=/raid1) svr428(rw,sync,nohide,mp=/raid1,all_squash,anonuid=40647,anongid=100) jaguar(rw,sync,no_root_squash,no_subtree_check)

Good luck!!!
 
Last edited:

Members online

No members online now.

Top