mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrew Morton <akpm@osdl.org>, Willy Weisz <weisz@vcpc.univie.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: Client looses NFS handle (kernel 2.6.3)
Date: Sun, 22 Feb 2004 02:12:05 -0800	[thread overview]
Message-ID: <1077444724.2944.10.camel@nidelv.trondhjem.org> (raw)
In-Reply-To: <20040221214345.6533eb68.akpm@osdl.org>

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@vcpc.univie.ac.at>
> To: linux-kernel@vger.kernel.org
> 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@vcpc.univie.ac.at
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

       reply	other threads:[~2004-02-22 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040221214345.6533eb68.akpm@osdl.org>
2004-02-22 10:12 ` Trond Myklebust [this message]
2004-02-23 13:15   ` Willy Weisz
2004-02-23 15:38     ` Trond Myklebust
2004-02-23 22:28   ` Chris Wright
2004-02-24  1:27     ` Trond Myklebust
2004-02-24  1:42       ` Chris Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1077444724.2944.10.camel@nidelv.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weisz@vcpc.univie.ac.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®