Re: Fw: Client looses NFS handle (kernel 2.6.3)

[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:
> fyi..
> 
> Begin forwarded message:
> 
> Date: Sun, 22 Feb 2004 00:36:13 +0100
> From: Willy Weisz <weisz@xxxxxxxxxxxxxxxxx>
> To: linux-kernel@xxxxxxxxxxxxxxx
> 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: weisz@xxxxxxxxxxxxxxxxx
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/