-Original Message-
From: Linux on 390 Port On Behalf Of Mauro Souza
A good way to know is running a showmount -e on the laptop.
If it returns the contents of your /etc/exports, we have to think about what
else could possibly be
wrong.
If don't, look on dmesg or /var/log/messages
Just for grins, after you do the mount, run 'exportfs -a' to force the exports
list to be updated.
[root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir
/tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0
/tmp/iso
mount.nfs: access denied by server
[root@localhost ~]# systemctl start nfs.service
[root@localhost ~]# mkdir /tmp/iso
[root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso
mount.nfs: access denied by server while mounting localhost:/dev/sr0
[root@localhost ~]#
Just for clarity, this part is on he laptop,
-Original Message-
From: Linux on 390 Port On Behalf Of David Boyes
Just for grins, after you do the mount, run 'exportfs -a' to force the
exports list to be updated.
[root@localhost ~]# exportfs -a
exportfs: /tmp/iso requires fsid= for NFS export
[root@localhost ~]# cat
[root@localhost ~]# exportfs -a
exportfs: /tmp/iso requires fsid= for NFS export [root@localhost ~]# cat
/etc/exports
/tmp/iso*(ro,no_root_squash)
[root@localhost ~]#
Perhaps the access denied message (below) has something to do with
this?
It does indeed, but it's not the problem
-Original Message-
From: Linux on 390 Port On Behalf Of Rick Troth
[root@localhost ~]# systemctl start nfs.service [root@localhost ~]#
mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock
localhost:/dev/sr0 /tmp/iso
mount.nfs: access denied by server while mounting
Try the -v flag on your mount. Perhaps verbose will give a clue of why it is
hanging.
The information contained in this e-mail message is intended only for the
personal and confidential use of the designated recipient(s) named above. This
message may be an
Looks like part of the problem is that both ends call themselves localhost.
DO NOT use localhost for the NFS mount (unless you really want to
NFS mount something served back to the same box, clearly not this
case).
...
[root@localhost ~]# mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso
-Original Message-
From: Linux on 390 Port On Behalf Of Veencamp, Jonathon D.
Try the -v flag on your mount. Perhaps verbose will give a clue of why it is
hanging.
[root@localhost ~]# mount -v localhost:/tmp/iso /tmp/testit
mount.nfs: timeout set for Thu Mar 7 10:26:19 2013
-Original Message-
From: Linux on 390 Port On Behalf Of Rick Troth
Looks like part of the problem is that both ends call themselves localhost.
DO NOT use localhost for the NFS mount (unless you really want to NFS mount
something served back to
the same box, clearly not this
Replying to myself
-Original Message-
-Original Message-
From: Linux on 390 Port On Behalf Of Rick Troth
Looks like part of the problem is that both ends call themselves
localhost.
DO NOT use localhost for the NFS mount (unless you really want to
NFS mount
... replacing 192.168.55.44 with the address of the laptop.
[root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit
mount.nfs: timeout set for Thu Mar 7 10:34:01 2013
mount.nfs: trying text-based options
'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67'
...
^C
[root@localhost
Hang in there, John. This will eventually work.
Here's what I get on the SLES install program on z/VM:
/ # mount 10.250.24.67:/tmp/iso /tmp/testit
/ # ls -l /tmp/testit
drwxr-xr-x2 00 40 Mar 7 16:45 .
drwxrwxrwt3 00 60 Mar 7 16:45 ..
The
-Original Message-
From: Linux on 390 Port On Behalf Of Rick Troth
[ snip ]
I often get timeout (or never-completing mount) when some magical part of the
RPC suite hasn't been
started. The server will need at least 'rpc.mountd'. I think the client
will need 'rpc.statd'. (I
14 matches
Mail list logo
