Prev: SSD firmware update
Next: Lost the key to a Sun 420R
From: Huub on 29 Jan 2010 07:46
Hi,

After installing Solaris 5.10 on a UltraSparc III+, I have perfect
connection to the internet, but can't connect to my nfs-server
(Slackware 12). With this vfstab entry:

Kaapstad:/admin - /mnt/Kaapstadadmin nfs - yes -

I get this error after mount -a :

nfs mount: Kaapstad:/admin: No such file or directory

Kaapstad is in the /etc/hosts file, so that's no problem. However,
looking at nfs:

> ps -ef | grep nfs
> daemon 282 1 0 09:02:26 ? 0:00 /usr/lib/nfs/lockd
> daemon 265 1 0 09:02:26 ? 0:00 /usr/lib/nfs/nfsmapid
> daemon 271 1 0 09:02:26 ? 0:00 /usr/lib/nfs/nfs4cbd
> daemon 267 1 0 09:02:26 ? 0:00 /usr/lib/nfs/statd

Makes me suspect I have nfs4 running, instead of nfs3. And the server
doesn't accept nfs4 connections. Can I safely (and easily) replace nfs4
by nfs3?

Thank you.
From: Casper H.S. Dik on 29 Jan 2010 07:51
Huub <v.niekerk_@_hccnet.nl> writes:

>Hi,

>After installing Solaris 5.10 on a UltraSparc III+, I have perfect
>connection to the internet, but can't connect to my nfs-server
>(Slackware 12). With this vfstab entry:

>Kaapstad:/admin - /mnt/Kaapstadadmin nfs - yes -

>I get this error after mount -a :

>nfs mount: Kaapstad:/admin: No such file or directory


I'm afraid that you need to create the directory /mnt/Kaapstadadmin
first.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
From: Chris Ridd on 29 Jan 2010 08:14
On 2010-01-29 12:46:15 +0000, Huub said:

> Makes me suspect I have nfs4 running, instead of nfs3. And the server
> doesn't accept nfs4 connections. Can I safely (and easily) replace nfs4
> by nfs3?

They should negotiate versions properly. But if there are problems with
using a negotiated version (NFSv4 from a Linux server is problematic)
you can edit /etc/default/nfs and force the Solaris NFS client to only
negotiate 3.

--
Chris

From: Huub on 29 Jan 2010 08:15
>> I get this error after mount -a :
>
>> nfs mount: Kaapstad:/admin: No such file or directory
>
>
> I'm afraid that you need to create the directory /mnt/Kaapstadadmin
> first.

Thanks for your answer. I should have mentioned I did create the directory:

# ls /mnt
Kaapstadadmin
# ls /mnt/Kaapstadadmin/
# ls -l /mnt/Kaapstadadmin/
total 0

So that's not the cause.

Any other suggestions?
From: Huub on 29 Jan 2010 08:18
On 01/29/10 14:14, Chris Ridd wrote:
> On 2010-01-29 12:46:15 +0000, Huub said:
>
>> Makes me suspect I have nfs4 running, instead of nfs3. And the server
>> doesn't accept nfs4 connections. Can I safely (and easily) replace
>> nfs4 by nfs3?
>
> They should negotiate versions properly. But if there are problems with
> using a negotiated version (NFSv4 from a Linux server is problematic)
> you can edit /etc/default/nfs and force the Solaris NFS client to only
> negotiate 3.
>

Thank you! This did the trick.
 |  Next  |  Last
Pages: 1 2
Prev: SSD firmware update
Next: Lost the key to a Sun 420R