From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 and NFS
Date: Tue, 07 Sep 2004 10:05:48 +0200 [thread overview]
Message-ID: <413D6BDC.80006@fh-landshut.de> (raw)
In-Reply-To: <1094543842.1340.61.camel@tribesman.namesys.com>
Hello Vladimir,
I guess not.
Both my clients are embedded systems, and both didn't work.
Client/Target one is a Motorola MVME2100 board with an MPC8240 PowerPC CPU @ 200
MHz.
Client/Target two is a Motorola MVME5500 board with an MPC7455 PowerPC CPU @ 1GHz.
Both failed to mount their root filesystem via NFS from a Reiser4 on the
server/host, but worked fine with an ext3 over NFS.
Either this is a NFSv3/Reiser4/2.6.8.1 server vs. NFSv3/2.4.21 client problem,
or it has something to do with endianness (PowerPC is big-endian, Intel P4 box
is little-endian). I know ext* has absolutely no issues with endianness, neither
as RAM disk nor over NFS, but perhaps Reiser4 has?
Do both your client and your server have kernel 2.6.x? Are both Reiser4 patched?
Maybe Linux 2.6.x has new LOOKUP operation semantics in order to support Reiser4
that Linux 2.4.2x hasn't?
On a side note:
It would be nice if we could reproduce the error, since I like Reiser4. I did a
large egrep over the whole /usr subtree, and didn't hear a sound from my hard
drive because accesses seemed to be well-ordered (no superfluous head
movements). I first thought the operation failed. ;)
With kind regards,
Oliver Korpilla
Vladimir Saveliev wrote:
> I have no problems with exporting reiser4 via NFS. Could it be that you
> have problem because your client is embedded?
next prev parent reply other threads:[~2004-09-07 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:53 Reiser4 and NFS Oliver Korpilla
2004-09-07 7:57 ` Vladimir Saveliev
2004-09-07 8:05 ` Oliver Korpilla [this message]
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=413D6BDC.80006@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.