From: Oliver Korpilla <okorpil@fh-landshut.de>
To: reiserfs-list@namesys.com
Subject: Reiser4 and NFS
Date: Mon, 06 Sep 2004 14:53:14 +0200 [thread overview]
Message-ID: <413C5DBA.1070207@fh-landshut.de> (raw)
Hello!
I've recently upgraded my Debian Sarge to use a Reiser4 as a root filesystem out
of curiosity.
I've been doing development on this box, involving serving a root filesystem to
an embedded target via NFS.
My box (the host) is a vanilla kernel.org Linux 2.6.8.1-mm1 with
reiser-all.diff.gz patchset. It's configured to serve NFSv3.
The target has a TimeSys 2.4.21 (realtime) Linux kernel with NFSv3 client support.
Before that, I've used 2.4.26 with an ext3 filesystem, and everything went fine.
Then I've upgraded kernel and my root filesystem (to Reiser4, I surely consider
that an upgrade! ;) ), and I get NFS error -45 (Operation not supported), when
target wants to do the LOOKUP operation (I can see that on Ethereal).
I've found a similar error occuring when serving VFAT partitions over NFS:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-02/7848.html
I've switched the particular subtree of my root FS that I want to serve via NFS
back to ext3, and the problem is gone, so this problem is clearly rooted in the
interaction between NFS and Reiser4.
If I were to do a wild guess, I'd say: Since both VFAT and Reiser4 directory
semantics differ from "standard Unix" (or at least ext*) conventions, this is
interferring with the NFS LOOKUP operation, don't you think?
I'll be glad to provide any additional information if required.
Thanks and with kind regards,
Oliver Korpilla
next reply other threads:[~2004-09-06 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:53 Oliver Korpilla [this message]
2004-09-07 7:57 ` Reiser4 and NFS Vladimir Saveliev
2004-09-07 8:05 ` Oliver Korpilla
2004-09-07 14:00 ` Vladimir Saveliev
2004-09-07 14:18 ` Oliver Korpilla
2004-09-08 12:00 ` Oliver Korpilla
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=413C5DBA.1070207@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--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.