mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: problems with nfs-server in 2.5 bk as of 030115
Date: 19 Jan 2003 22:39:34 +0100	[thread overview]
Message-ID: <1043012373.7986.94.camel@tux.rsn.bth.se> (raw)

Hi Trond,

This is the first time I've tried running an nfs-server in 2.5 and I
believe the problem I'm seeing is caused by your recent changes.

This kernel includes the two fixes you made.
"[PATCH] Fix RPC client warning in 2.5.58..."
and
"[PATCH] Fix NFS root mount handling"

I havn't seen any nfs/rpc related changes since these patches.

This is what I get when trying to start the nfs-server
(/etc/init.d/nfs-kernel-server in debian):

Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
RPC: Couldn't create pipefs entry /portmap/clntcfac0540
RPC: Couldn't create pipefs entry /portmap/clntcfac0540
RPC: Couldn't create pipefs entry /portmap/clntcfac0540

I've mounted the rpc_pipefs filesystem and the directory
portmap/clntcfac0540 is created. It's empty but created.
It gets created with 500 as permissions.

the directories at the root of the rpc_pipefs filesystem get created
correctly with the permissions that your patch changed but not the
entries in these directories.

portmap does run as user daemon on this system.

I did check to make sure your patches were included and they were.

Output from rpcinfo:
# rpcinfo -p localhost
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  32832  mountd
    100005    1   tcp  35561  mountd
    100005    2   udp  32832  mountd
    100005    2   tcp  35561  mountd

modules loaded:

nfsd                  118640  0 
exportfs                4224  1 nfsd
lockd                  61040  1 nfsd
sunrpc                115844  3 nfsd,lockd

relevant parts of .config:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y 
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m

kernel compiled with gcc 3.2.2 if that matters.

Looking forward to suggestions/patches to test :)

-- 
/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.

             reply	other threads:[~2003-01-19 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 21:39 Martin Josefsson [this message]
2003-01-19 22:05 ` Trond Myklebust
2003-01-19 22:50   ` Martin Josefsson
2003-01-19 23:22     ` Martin Josefsson
2003-01-19 23:24     ` Trond Myklebust
2003-01-20  0:17       ` Martin Josefsson
2003-01-20  1:00         ` Trond Myklebust
2003-01-20  1:17           ` Martin Josefsson
2003-01-20  1:20             ` Trond Myklebust
2003-01-20  1:26               ` Martin Josefsson
2003-01-20  1:34 ` Trond Myklebust
2003-01-20  1:50   ` Martin Josefsson
2003-01-20  2:01     ` Trond Myklebust
2003-01-20  2:17       ` Martin Josefsson

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=1043012373.7986.94.camel@tux.rsn.bth.se \
    --to=gandalf@wlug.westbo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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®