archive mirror
 help / color / mirror / Atom feed
From: Wakko Warner <>
To: Neil Brown <>
Subject: Re: 2.6.x NFS and NFSD
Date: Fri, 1 Aug 2003 21:02:05 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <16169.58331.996181.236352@gargle.gargle.HOWL>; from Neil Brown on Fri, Aug 01, 2003 at 01:51:55PM +1000

> > 2.6.x as a server:
> > I'm using nfs-kernel-server v1.0.5-1 (debian).
> > Config Ops:
> > # CONFIG_NFSD_V4 is not set
> > CONFIG_LOCKD_V4=y   << I didn't configure this, where'd it come
> > from?
> If either NFS_V3 or NFSD_V3, then LOCKD_V4 is automatically added.

Ok, I see.

> > This is in /etc/exports:
> > / vegeta(rw,no_root_squash,async,nohide)
> "nohide" is incorrect here.

previous experience.  IIRC, if I didn't have it on /, I couldn't see /usr,
/raid-0, or others (2.4.x).

> > ls, and ls hangs.  client uses kernel 2.4.20 with NFSv3 enabled and it was
> > mounted v3.
> I have a hunch what this might be, and it'll require fixing both the
> kernel and nfs-utils ;-(
> Could you try using
>    mount -t nfsd nfsd /proc/fs/nfs

This worked.  Of course I also removed nohide from / and added the rest of
my FSs.  There were 4 in all on this test machine. / /usr /usr/src and
/home.  All are exported as above except / has nohide removed.

> before starting the nfs-kernel-server (particularly before starting
> mountd or running exportfs).
> Also, if you are brave, could you try with the following two patches,
> one against linux-2.6.0-test2 and one against nfs-utils.  Then run the
> nfs kernel server *without* mounting /proc/fs/nfs first.

I did not try the patches.  This work around seems to be what I was looking
for.  I'll wait for the patches to be merged.  I did not patch the
nfs-kernel-server either.

I tried 2.6.x as a client to a v2 server running the userland server.  I do
get a ton of nfs not responding messages, but I did a find /mnt/usr on it. 
Doesn't seem to be going into D state this time.

 Lab tests show that use of micro$oft causes cancer in lab animals

      reply	other threads:[~2003-08-02  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 22:51 2.6.x NFS and NFSD Wakko Warner
2003-08-01  3:51 ` Neil Brown
2003-08-02  1:02   ` Wakko Warner [this message]

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).