All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 20:08:49 +0200	[thread overview]
Message-ID: <01060220084900.04097@athlon> (raw)
In-Reply-To: <E156E7j-0001su-00@the-village.bc.nu>
In-Reply-To: <E156E7j-0001su-00@the-village.bc.nu>

Am Samstag,  2. Juni 2001 18:19 schrieben Sie:
> > I got massive file corruptions with the kernels mentioned in the subject.
> > I can reproduce it every time.
>
> Which other 2.4 trees have you tried ?

I had the following situations:

NFS server:
linux 2.2.19

NFS Client:
linux 2.4.[32]ac[...],
linux 2.4.4ac[1-...]
[1-10] have been working fine. Beginning with ac11, I got the problems I 
wrote. During this time, I never used any knfsd-patch.



The following is the combination, which seems to be working fine:

NFS Server:
linux 2.2.19 with knfsd-patch or linux 2.4.5 with the following knfsd-Patch 
from Gergely Tamas <dice@mfa.kfki.hu> (I got it from the mailinglist of 
reiser) (there is no patch for ac6):

--------------------------------------------------------------------------------------
--- linux-2.4.5/fs/inode.c.orig Fri May 25 14:15:38 2001
+++ linux-2.4.5/fs/inode.c      Wed May 30 12:17:29 2001
@@ -1044,6 +1044,8 @@
                                inode->i_state|=I_FREEING;
                                inodes_stat.nr_inodes--;
                                spin_unlock(&inode_lock);
+                               if (inode->i_data.nrpages)
+                                       truncate_inode_pages(&inode->i_data, 
0);
                                clear_inode(inode);
                        }
                }

--- linux-2.4.5-pre6/fs/nfs/dir.c.orig  Fri May 25 14:15:38 2001
+++ linux-2.4.5-pre6/fs/nfs/dir.c       Thu May 31 14:53:32 2001
@@ -753,6 +753,8 @@

        nfs_zap_caches(dir);
        error = NFS_PROTO(dir)->rmdir(dir, &dentry->d_name);
+       if (!error)
+               dentry->d_inode->i_nlink -= 2;

        return error;
 }
@@ -870,6 +872,8 @@
        error = NFS_PROTO(dir)->remove(dir, &dentry->d_name);
        if (error < 0)
                goto out;
+       if (inode)
+               inode->i_nlink--;

  out_delete:
        /*
------------------------------------------------------------------------

I patched the original 2.4.5-sources.

NFS Client:
linux 2.4.5 with knfsd-patch.

I need the patch on both the server and the client to get it working.

>
> Does booting with ide=nodma help ? [only in -ac]

I tested the following combination:

Server
2.2.19 without knfsd-Patch

Client
2.4.5ac6 without knfsd-Patch but ide=nodma

Result:
IO-Errors as I wrote in my initial posting.


Regards
Adnreas Hartmann

      reply	other threads:[~2001-06-02 18:17 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
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 [this message]

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=01060220084900.04097@athlon \
    --to=andihartmann@freenet.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.