From: dek_ml@konerding.com
To: linux-kernel@vger.kernel.org
Subject: problems with reiserfs + nfs using 2.4.2-pre4
Date: Sun, 18 Feb 2001 16:18:11 -0800 [thread overview]
Message-ID: <200102190018.f1J0IBo08575@konerding.com> (raw)
Hi,
I migrated some exported disks over to reiserfs and had no luck when I
mounted the disk via NFS on another machine. I've noticed many messages
about reiser and NFS in the archives, but my understanding was that
it had been cleared up. In particular, the Configure.help in 2.4.2-pre4
says "reiserfs can be used for anything that ext2 can be used for".
Here's my setup:
server box running RH71beta, kernel 2.4.2-pre4 compiled with gcc-2.95.2.
client box running RH71beta, kernel 2.4.2-pre4 compiled with gcc-2.95.2.
On the server, I built a standard kernel with NFS server, LVM, and reiser.
On the client, I built a standard kernel with NFS client.
On the server, the filesystem was created over an LVM logical volume.
When I mounted the server-exported filesystem on the client node,
there are no visible files or directories. Reverting to ext2 fixed the problem.
I'd like to hear from people who have tried recent 2.4 kernels with RH7.1,
NFS, and reiser, to see if anybody has had luck.
Dave
next reply other threads:[~2001-02-19 0:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 0:18 dek_ml [this message]
2001-02-19 0:37 ` problems with reiserfs + nfs using 2.4.2-pre4 Neil Brown
2001-02-19 2:56 ` dek_ml
2001-02-19 3:40 ` Neil Brown
2001-02-19 11:23 ` Alan Cox
2001-02-20 0:40 ` Neil Brown
2001-02-20 1:15 ` Chris Mason
2001-02-20 1:34 ` Neil Brown
2001-02-20 1:24 ` Alan Cox
2001-02-20 1:37 ` Neil Brown
2001-02-20 2:11 ` dek_ml
2001-02-20 22:54 ` Brian May
2001-02-20 23:30 ` Chris Mason
2001-02-20 2:38 ` Roman Zippel
2001-02-20 9:44 ` [NFS] " Trond Myklebust
2001-02-20 14:02 ` Roman Zippel
2001-02-20 15:16 ` Trond Myklebust
2001-02-20 16:26 ` Roman Zippel
2001-02-21 3:02 ` Neil Brown
2001-02-21 12:43 ` [NFS] " Trond Myklebust
2001-02-19 1:55 ` Alan Cox
2001-02-19 15:37 ` Chris Mason
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=200102190018.f1J0IBo08575@konerding.com \
--to=dek_ml@konerding.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox