From: Chris Mason <mason@suse.com>
To: "Andreas Hartmann" <andihartmann@freenet.de>,
"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, 02 Jun 2001 12:42:04 -0400 [thread overview]
Message-ID: <273360000.991500124@tiny> (raw)
In-Reply-To: <01060214363800.02172@athlon>
On Saturday, June 02, 2001 02:41:04 PM +0200 Andreas Hartmann
<andihartmann@freenet.de> wrote:
> 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?
The problem only happens when the clients do an operation on a file that
has gone out of cache on the server. Under light load, this might happen
very rarely.
You only need the patch on the server.
-chris
next prev parent reply other threads:[~2001-06-02 16:47 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
2001-06-02 16:42 ` Chris Mason [this message]
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=273360000.991500124@tiny \
--to=mason@suse.com \
--cc=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