All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: reiserfs-list@namesys.com
Cc: "Markus Törnqvist" <mjt@nysv.org>, linux-fai@rrz.uni-koeln.de
Subject: Re: NFSv2 problem? initctl problem?
Date: Thu, 19 Aug 2004 12:56:34 +0200	[thread overview]
Message-ID: <200408191256.40317.bernd-schubert@web.de> (raw)
In-Reply-To: <20040818145103.GE1284@nysv.org>

[-- Attachment #1: Type: text/plain, Size: 2998 bytes --]


> It doesn't matter whether I use the kernel- or user-space NFS
> implementation, it still dies on me, except that I'd rather use the
> kernel-space one.

Don't use te unfsd except for special reasons. If you want to test a userspace 
daemon just use unfs3 (unfs3.sf.net).

>
> Now what I'm wondering about is where is the error?
>
> How can I force the client to use only NFSv3? rpc.mountd -N2 -V3 should
> work, right? But it still speaks v2 according to the traffic AND affects
> only the server-side, in theory, if not in practice apparently.

"man 5 nfs", mountoption is "nfsvers=3"

>
> The underlying filesystem is ReiserFS, so I'm sending a copy of this
> mail to the ReiserFS list as well, to see if anyone over there knows
> anything about this. If need be, I can reinstall the FAI server to use
> some other FS, but I would not like to do that.
>
> With the user-space NFS implementation I got the file id of 1476542499
> which does not have a file in the file system at all. Might this be
> because of ReiserFS? An ancient curse? NFS just being broken?

I wouldn't use the old userspace daemon with reiserfs at all, if you want to 
do this, just use unfs3.

>
> Any help is greatly appreciated here, I have a deadline coming up for
> this installation and just out of principle I would dislike doing it
> from a CD as I'm going to install a lot more of these Debians and need
> FAI working...

Well, your testing approach is a bit strange:

1.) I would use the knfsd.
2.) To test if exporting works, I would take a second non-rootnfs system and 
try to mount the exported directories on this system. This will help you a 
lot since you can experiment with mount options on this system and you can 
check the syslogs.
3.) I mounting from you second server works, you can go on and see what 
happens in your fai environment.

>
> PS.
> Semi-off topic, what's the status of NFSv4? rpc.mountd supports something
> like it but is it in Linux already?
> Should I seek answers elsewhere than in 0d NFS protocols?

Your questions are completety off topic from the view of reiserfs, since there 
are many people (including our group) who use nfs and reiserfs. However you 
should use unfsd and reiserfs. A group suitable for nfs questions is 
"nfs@lists.sourceforge.net".  NFSv4 is still in early development and I 
wouldn't use it except for some tests (actually I never used it at all, but I 
see all of those patches about it on the nfs-list).


Cheers, 
	Bernd

PS: If you should decide to unfs3 for some tests, make sure it is able to 
include the ext2_fs.h, unfortunality the one from the debian kernel-headers 
package is broken :(, replace it with the file from Mariusz Mazur headers 
(http://ep09.pld-linux.org/~mmazur/linux-libc-headers/)


-- 
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-19 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 14:51 NFSv2 problem? initctl problem? mjt
2004-08-19 10:56 ` Bernd Schubert [this message]
2004-08-19 11:30   ` mjt

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=200408191256.40317.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=linux-fai@rrz.uni-koeln.de \
    --cc=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.