From: Andreas Hartmann <andihartmann@freenet.de>
To: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>
Cc: Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.5 and all ac-Patches] massive file corruption with reiser or NFS
Date: Sat, 2 Jun 2001 14:41:04 +0200 [thread overview]
Message-ID: <01060214363800.02172@athlon> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0106021251570.1083-100000@grignard.amagerkollegiet.dk>
In-Reply-To: <Pine.LNX.4.33L2.0106021251570.1083-100000@grignard.amagerkollegiet.dk>
Am Samstag, 2. Juni 2001 12:52 schrieb Rasmus Bøg Hansen:
> On Sat, 2 Jun 2001, Andreas Hartmann wrote:
> > I got massive file corruptions with the kernels mentioned in the subject.
> > I can reproduce it every time.
>
> You cannot use NFS on reiserfs unless you apply the knfsd patch. Look at
> www.namesys.com.
Thank you very much for your advice.
I tested your suggestion and run the machine without NFS-mounted devices - it
seems to be working fine.
Anyway - I'm wondering why I didn't get any problem until 2.4.4ac10 with this
configuration without the appropriate patch on the client or on the server?
I'm a little bit confused now about this patch.
Do I need this knfsd-patch for the NFS-server or just for the clients or for
both?
Thank you for your advice,
Andreas Hartmann
next prev parent reply other threads:[~2001-06-02 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 10:34 [2.4.5 and all ac-Patches] massive file corruption with reiser or NFS Andreas Hartmann
2001-06-02 10:52 ` Rasmus Bøg Hansen
2001-06-02 12:41 ` Andreas Hartmann [this message]
2001-06-02 16:42 ` Chris Mason
2001-06-02 18:13 ` Andreas Hartmann
2001-06-02 18:33 ` Chris Mason
2001-06-02 20:02 ` Andreas Hartmann
2001-06-02 16:19 ` Alan Cox
2001-06-02 18:08 ` Andreas Hartmann
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=01060214363800.02172@athlon \
--to=andihartmann@freenet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
/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