archive mirror
 help / color / mirror / Atom feed
From: Wakko Warner <>
Subject: 2.6.x NFS and NFSD
Date: Wed, 30 Jul 2003 18:51:15 -0400	[thread overview]
Message-ID: <> (raw)

Anyone had any luck with either of these?

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?
This is in /etc/exports:
/ vegeta(rw,no_root_squash,async,nohide)

on the machine vegeta, I mount this machine (kingkai:/ /mnt), cd to /mnt, do
ls, and ls hangs.  client uses kernel 2.4.20 with NFSv3 enabled and it was
mounted v3.

2.6.x as a client:
If the server is using 2.4.x with the kernel nfs server, all's fine except
for nohide.  I have a 2.4.21 alpha machine exporting / and /raid-0 with the
nohide option.  If I mount it to /mnt and cd /mnt/raid-0 there's nothing
there.  On 2.4.20 client this works. (NFSv3 here)

If the server is using the userspace nfs server (I don't like exporting all
those mount points with nohide and this works for me on most machines that I
access occasionally.  I assume userspace is NFSv2. 2.2beta47-12) Kernel
2.6.x will simply say the nfs server is not responding if I do an ls.  If I
copy a file (not using tab completion), it seems to work.

client options:
# CONFIG_NFS_V4 is not set

Now on a positive note, my hp scanjet 5370c works with 2.6.0-test2 great
where as 2.4 it doesn't.  the NFS is holding me back.

Vegeta: kernel 2.4.20, userspace nfs, inspiron 8100 1ghz pIII 256mb ram
	NIC: intel 10/100
Kingkai: Kernel 2.6.0-test1, kernel nfs, home build 700mhz pIII 256mb ram
	NIC: 3com 3cr990srv 10/100   MainBoard: MSI MS-6163 v2
Alpha: Kernel 2.4.21, kernel nfs, AlphaServer 1000A 4/266 160mb ram
	NIC: Dec Tulip 10/100

All machines use ext3 as the local filesystem.

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

             reply	other threads:[~2003-07-30 22:35 UTC|newest]

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

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).