OpenSolaris

Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » nfs » discuss

Thread: NFS mounting problem

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 7 - Last Post: Sep 25, 2005 2:27 PM by: boyd
erisch

Posts: 30
From: US

Registered: 6/15/05
NFS mounting problem
Posted: Sep 24, 2005 5:03 PM

  Click to reply to this thread Reply

Hi

I have a problem with mounting a linux-provided share into my opensolaris system: I get the "Not owner" error, although I set NFS_CLIENT_VERSMAX to 3. Even when I pass vers=3 as option to the mount command I get this error. I also tried some other options like sec=... but I cant get a solution.

I sniffed the packets which were send, and the client is definitely using NFSv3.

With Solaris Express all worked fine, but after I bfu'ed I get this problems.

Has anybody an idea how to solve this?

Thanks in advance
erisch

Environment: Solaris Express B19, opensolaris-src-20050909, sparc
I tried the bfu archives and the selfcompiled sources: same effect

rbg

Posts: 79
From: US

Registered: 6/7/05
Re: NFS mounting problem
Posted: Sep 24, 2005 5:48 PM   in response to: erisch

  Click to reply to this thread Reply

Erik;

Providing the snoop output would be handy.

Did you also use the closed bits for 20050909 ?

-- Robert...
"Procrastination is the thief of time"

On Sep 24, 2005, at 7:03 PM, Erik Trauschke wrote:

> Hi
>
> I have a problem with mounting a linux-provided share into my
> opensolaris system: I get the "Not owner" error, although I set
> NFS_CLIENT_VERSMAX to 3. Even when I pass vers=3 as option to the
> mount command I get this error. I also tried some other options like
> sec=... but I cant get a solution.
>
> I sniffed the packets which were send, and the client is definitely
> using NFSv3.
>
> With Solaris Express all worked fine, but after I bfu'ed I get this
> problems.
>
> Has anybody an idea how to solve this?
>
> Thanks in advance
> erisch
>
> Environment: Solaris Express B19, opensolaris-src-20050909, sparc
> I tried the bfu archives and the selfcompiled sources: same effect
> This message posted from opensolaris.org
> _______________________________________________
> nfs-discuss mailing list
> nfs-discuss at opensolaris dot org
>

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



erisch

Posts: 30
From: US

Registered: 6/15/05
Re: NFS mounting problem
Posted: Sep 25, 2005 8:52 AM   in response to: rbg

  Click to reply to this thread Reply

Am So, den 25.09.2005 schrieb Robert Gordon um 2:48:
> Erik;
>
> Providing the snoop output would be handy.
>
I hope tcpdump output will also help ;)

moo is my internal domain, phoebe is the linux box with the nfs server,
10.0.0.50 is the solaris nfs client (its name is not resolved by the dns
server yet)

***************************************************************
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
17:36:07.128579 IP 10.0.0.50.63489 > phoebe.moo.sunrpc: UDP, length: 56
17:36:07.129684 IP phoebe.moo.sunrpc > 10.0.0.50.63489: UDP, length: 28
17:36:07.130276 IP 10.0.0.50.63489 > phoebe.moo.781: UDP, length: 40
17:36:07.130640 IP phoebe.moo.781 > 10.0.0.50.63489: UDP, length: 24
17:36:07.132132 IP 10.0.0.50.976 > phoebe.moo.781: UDP, length: 136
[...]
17:36:07.258098 IP phoebe.moo.781 > 10.0.0.50.976: UDP, length: 56
17:36:07.266240 IP 10.0.0.50.50920 > phoebe.moo.sunrpc: UDP, length: 56
17:36:07.268070 IP phoebe.moo.sunrpc > 10.0.0.50.50920: UDP, length: 28
17:36:07.271088 IP 10.0.0.50.53175 > phoebe.moo.2049: S
989509317:989509317(0) w in 49640 <mss 1460,nop,wscale 0,nop,nop,sackOK>
17:36:07.271197 IP phoebe.moo.2049 > 10.0.0.50.53175: S
3410208344:3410208344(0) ack 989509318 win 5840 <mss
1460,nop,nop,sackOK,nop,wscale 2>
17:36:07.271582 IP 10.0.0.50.53175 > phoebe.moo.2049: . ack 1 win 49640
17:36:07.272736 IP 10.0.0.50.1127471020 > phoebe.moo.nfs: 116 null
17:36:07.272780 IP phoebe.moo.2049 > 10.0.0.50.53175: . ack 117 win 1460
17:36:07.293421 IP phoebe.moo.2049 > 10.0.0.50.53175: P 1:29(28) ack 117
win 146 0
17:36:07.293684 IP 10.0.0.50.53175 > phoebe.moo.2049: . ack 29 win 49640
17:36:07.294110 IP 10.0.0.50.53175 > phoebe.moo.2049: F 117:117(0) ack
29 win 49 640
17:36:07.307134 IP phoebe.moo.2049 > 10.0.0.50.53175: F 29:29(0) ack 118
win 146 0
17:36:07.307439 IP 10.0.0.50.53175 > phoebe.moo.2049: . ack 30 win 49640
17:36:07.355021 IP 10.0.0.50.686493318 > phoebe.moo.nfs: 132 fsinfo
[|nfs]
17:36:07.372434 IP phoebe.moo.nfs > 10.0.0.50.686493318: reply ok 36
fsinfo ERRO R: Operation not permitted
17:36:07.372802 IP 10.0.0.50.55519 > phoebe.moo.2049: . ack 3373981359
win 49640
***********************************************************************

> Did you also use the closed bits for 20050909 ?

I did everything like it was adviced in the release notes. Is there
anything special I have to care about?

erisch

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



rbg

Posts: 79
From: US

Registered: 6/7/05
Re: NFS mounting problem
Posted: Sep 25, 2005 10:49 AM   in response to: erisch

  Click to reply to this thread Reply


As root on the OpenSolaris Client try this:

# echo "clnt_cots_do_bindresvport/W 1" | mdb -kw

and retry the mount.

-- Robert..

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



erisch

Posts: 30
From: US

Registered: 6/15/05
Re: NFS mounting problem
Posted: Sep 25, 2005 11:06 AM   in response to: rbg

  Click to reply to this thread Reply

Thank you, that works perfect.

Can you please explain what happens here?
And is this a general bug?

erisch

Am So, den 25.09.2005 schrieb Robert Gordon um 19:49:
> As root on the OpenSolaris Client try this:
>
> # echo "clnt_cots_do_bindresvport/W 1" | mdb -kw
>
> and retry the mount.
>
> -- Robert..
>
>

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



rbg

Posts: 79
From: US

Registered: 6/7/05
Re: NFS mounting problem
Posted: Sep 25, 2005 11:41 AM   in response to: erisch

  Click to reply to this thread Reply

Erik;

Good! -- Could you please report the distribution/version of Linux and
the patch
level of the NFS server you are using?

OpenSolaris-20050909 is build 22. In build 22 the default behavior for
the NFS
client when establishing a connection to a server has been changed to
use
a port number greater than 1024 (a port number that is not reserved).

Setting clnt_cots_do_bindresvport to 1 changes the default to use a
reserved port
for TCP connections (clnt_clts_do_bindresvport for UDP).

Add the following line to /etc/system to make this the default on
reboot.

set rpcmod:clnt_cots_do_bindresvport=1

-- Robert...
"Procrastination is the thief of time"

On Sep 25, 2005, at 1:06 PM, Erik Trauschke wrote:
> Thank you, that works perfect.
>
> Can you please explain what happens here?
> And is this a general bug?
>
> erisch
>
> Am So, den 25.09.2005 schrieb Robert Gordon um 19:49:
>> As root on the OpenSolaris Client try this:
>>
>> # echo "clnt_cots_do_bindresvport/W 1" | mdb -kw
>>
>> and retry the mount.
>>
>> -- Robert..
>>
>>
>
> _______________________________________________
> nfs-discuss mailing list
> nfs-discuss at opensolaris dot org
>

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



erisch

Posts: 30
From: US

Registered: 6/15/05
Re: NFS mounting problem
Posted: Sep 25, 2005 11:53 AM   in response to: rbg

  Click to reply to this thread Reply

Hi

Thanks for the answers.

Am So, den 25.09.2005 schrieb Robert Gordon um 20:41:
> Erik;
>
> Good! -- Could you please report the distribution/version of Linux and
> the patch
> level of the NFS server you are using?

Gentoo Linux, Kernel 2.6.11-ck7 (Con Kolivas patched)
nfs-utils 1.0.6


erisch

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org



boyd

Posts: 202
From: AU

Registered: 6/14/05
Re: NFS mounting problem
Posted: Sep 25, 2005 2:27 PM   in response to: rbg

  Click to reply to this thread Reply

On my Debian based server, I can also use the "insecure" export
option to allow connection from non-reserved ports.

On 26/09/2005, at 4:41 AM, Robert Gordon wrote:

> Erik;
>
> Good! -- Could you please report the distribution/version of Linux
> and the patch
> level of the NFS server you are using?
>
> OpenSolaris-20050909 is build 22. In build 22 the default behavior
> for the NFS
> client when establishing a connection to a server has been changed
> to use
> a port number greater than 1024 (a port number that is not reserved).
>
> Setting clnt_cots_do_bindresvport to 1 changes the default to use a
> reserved port
> for TCP connections (clnt_clts_do_bindresvport for UDP).
>
> Add the following line to /etc/system to make this the default on
> reboot.
>
> set rpcmod:clnt_cots_do_bindresvport=1
>
> -- Robert...
> "Procrastination is the thief of time"
>
> On Sep 25, 2005, at 1:06 PM, Erik Trauschke wrote:
>
>> Thank you, that works perfect.
>>
>> Can you please explain what happens here?
>> And is this a general bug?
>>
>> erisch
>>
>> Am So, den 25.09.2005 schrieb Robert Gordon um 19:49:
>>
>>> As root on the OpenSolaris Client try this:
>>>
>>> # echo "clnt_cots_do_bindresvport/W 1" | mdb -kw
>>>
>>> and retry the mount.
>>>
>>> -- Robert..
>>>
>>>
>>
>> _______________________________________________
>> nfs-discuss mailing list
>> nfs-discuss at opensolaris dot org
>>
>>
>
> _______________________________________________
> nfs-discuss mailing list
> nfs-discuss at opensolaris dot org
>
>

_______________________________________________
nfs-discuss mailing list
nfs-discuss at opensolaris dot org






Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
© 2010, Oracle Corporation and/or its affiliates

Oracle