Skip to contentSkip to conversation

Client looses NFS handle (kernel 2.6.3)

DISCUSSION Trond Myklebust 3 participants 6 messages Feb 22, 2004 – Feb 24, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

The "Can't bind to reserved port" error message looks like the known problem when you set CONFIG_SECURITY. It has been discussed several times already on l-k.

Please either disable CONFIG_SECURITY (it's not as if *that* is going to be a showstopper when migrating to 2.6.x from 2.4.x) or go to my website and apply the advertised fix:

http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.3/linux-2.6.3-08-reconnect.dif

Cheers,
Trond

På lau , 21/02/2004 klokka 21:43, skreiv Andrew Morton:

Quoted 50 lines

fyi..

Begin forwarded message:

Date: Sun, 22 Feb 2004 00:36:13 +0100
From: Willy Weisz <[email protected]>
To: [email protected]
Subject: Client looses NFS handle (kernel 2.6.3)

The client looses the handle to a statically mounted NFS file system. A user sees
a stale handle in "df" and can't access files and directories.

When root issues a "df" or accesses a file or directory on the NFS file system,
it gets a correct result.

Thereafter a normal user also can access files and directories on the NFS file system.
After a short time the NFS handle becomes stale again. /var/log/messages contains the lines:

Feb 21 23:33:50 gsr108 kernel: RPC: Can't bind to reserved port (13).
Feb 21 23:33:50 gsr108 kernel: RPC: can't bind to reserved port.

after a user tries to access a file on the NFS file system. The NFS server runs kernel version 2.4.23 SMP. Client NFS 2.4.23 works.

The filesystem is mounted with the following options in /etc/fstab:
rw,bg,hard,intr,rsize=8192,wsize=8192

We are stuck and can't upgrade to 2.6.x with this bug.

Regards

Willy Weisz
-----------------------------------------------------------
Willy Weisz

European Centre for Parallel Computing at Vienna (VCPC)

                 Liechtensteinstrasse 22
                 A-1090 Wien

Tel: (+43 1) 4277 - 38824 Fax: (+43 1) 4277 - 9388
e-mail: [email protected]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw

Dear Trond,

thank you for the fast reply. I chose the first solution (unsetting CONFIG_SECURITY) as I don't have local security modules anyhow. and our problem disapeared.

Is there any reason to nevertheless install your patch?

Cheers

Willy

Quoted 71 lines · Trond Myklebust

The "Can't bind to reserved port" error message looks like the known problem when you set CONFIG_SECURITY. It has been discussed several times already on l-k.

Please either disable CONFIG_SECURITY (it's not as if *that* is going to be a showstopper when migrating to 2.6.x from 2.4.x) or go to my website and apply the advertised fix:

http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.3/linux-2.6.3-08-reconnect.dif

Cheers,
Trond

På lau , 21/02/2004 klokka 21:43, skreiv Andrew Morton:

Quoted 49 lines

fyi..

Begin forwarded message:

Date: Sun, 22 Feb 2004 00:36:13 +0100
From: Willy Weisz <[email protected]>
To: [email protected]
Subject: Client looses NFS handle (kernel 2.6.3)

The client looses the handle to a statically mounted NFS file system. A user sees a stale handle in "df" and can't access files and directories.

When root issues a "df" or accesses a file or directory on the NFS file system, it gets a correct result.

Thereafter a normal user also can access files and directories on the NFS file system. After a short time the NFS handle becomes stale again.
/var/log/messages contains the lines:

Feb 21 23:33:50 gsr108 kernel: RPC: Can't bind to reserved port (13).
Feb 21 23:33:50 gsr108 kernel: RPC: can't bind to reserved port.

after a user tries to access a file on the NFS file system. The NFS server runs kernel version 2.4.23 SMP. Client NFS 2.4.23 works.

The filesystem is mounted with the following options in /etc/fstab:
rw,bg,hard,intr,rsize=8192,wsize=8192

We are stuck and can't upgrade to 2.6.x with this bug.

Regards

Willy Weisz
-----------------------------------------------------------
Willy Weisz

European Centre for Parallel Computing at Vienna (VCPC)

                Liechtensteinstrasse 22
                A-1090 Wien

Tel: (+43 1) 4277 - 38824 Fax: (+43 1) 4277 - 9388
e-mail: [email protected]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 8 lines
-----------------------------------------------------------
Willy Weisz

European Centre for Parallel Computing at Vienna (VCPC)
                Liechtensteinstrasse 22
                A-1090 Wien
Tel: (+43 1) 4277 - 38824          Fax: (+43 1) 4277 - 9388
               e-mail: [email protected]
#3 lore raw

På må , 23/02/2004 klokka 05:15, skreiv Willy Weisz:

Quoted 7 lines

Dear Trond,

thank you for the fast reply. I chose the first solution (unsetting CONFIG_SECURITY)
as I don't have local security modules anyhow. and our problem disapeared.

Is there any reason to nevertheless install your patch?

No: the patch solves just the one problem.

Cheers,
Trond

#4 lore raw
In reply to Trond Myklebust
Quoted 9 lines · * Trond Myklebust ([email protected]) wrote:

The "Can't bind to reserved port" error message looks like the known problem when you set CONFIG_SECURITY. It has been discussed several times already on l-k.

Please either disable CONFIG_SECURITY (it's not as if *that* is going to be a showstopper when migrating to 2.6.x from 2.4.x) or go to my website and apply the advertised fix:

http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.3/linux-2.6.3-08-reconnect.dif

Looks nice. Will this go upstream, or is there still other issue?

thanks,
-chris

Signature · 1 line
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
#5 lore raw

På må , 23/02/2004 klokka 14:28, skreiv Chris Wright:

Quoted 4 lines
Quoted 2 lines

http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.3/linux-2.6.3-08-reconnect.dif

Looks nice. Will this go upstream, or is there still other issue?

No known issues, so I expect it to go upstream RSN. I just thought it would be convenient to make use of the fact that the Connectathon inter-vendor testfest is on right now to give it some extra milage first ;-).

Cheers,
Trond

#6 lore raw
Quoted 10 lines · * Trond Myklebust ([email protected]) wrote:

På må , 23/02/2004 klokka 14:28, skreiv Chris Wright:

Quoted 4 lines
Quoted 2 lines

http://www.fys.uio.no/~trondmy/src/Linux-2.6.x/2.6.3/linux-2.6.3-08-reconnect.dif

Looks nice. Will this go upstream, or is there still other issue?

No known issues, so I expect it to go upstream RSN. I just thought it would be convenient to make use of the fact that the Connectathon inter-vendor testfest is on right now to give it some extra milage first ;-).

Heh, sounds good. Thanks ;-)
-chris

Signature · 1 line
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net