[571] in arla-drinkers
Re: frequent cache corruption with arla 0.21 on linux 2.2.1
daemon@ATHENA.MIT.EDU (Magnus Ahltorp)
Thu Feb 4 11:28:49 1999
From owner-arla-drinkers@stacken.kth.se Thu Feb 04 16:28:49 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 20630 invoked from network); 4 Feb 1999 16:28:48 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 4 Feb 1999 16:28:48 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA01032
for arla-drinkers-list; Thu, 4 Feb 1999 17:23:11 +0100 (MET)
Received: from squid.pdc.kth.se (squid.pdc.kth.se [130.237.221.65])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA01028
for <arla-drinkers@stacken.kth.se>; Thu, 4 Feb 1999 17:23:05 +0100 (MET)
Received: (from d95-mah@localhost)
by squid.pdc.kth.se (8.8.7/8.8.7) id RAA15581;
Thu, 4 Feb 1999 17:22:46 +0100 (MET)
To: "Neulinger, Nathan R." <nneul@umr.edu>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: frequent cache corruption with arla 0.21 on linux 2.2.1
References: <9DA8D24B915BD1118911006094516EAF019C7ECA@umr-mail02.cc.umr.edu>
From: Magnus Ahltorp <map@stacken.kth.se>
Date: 04 Feb 1999 17:22:46 +0100
In-Reply-To: "Neulinger, Nathan R."'s message of "Thu, 4 Feb 1999 09:25:44 -0600"
Message-ID: <ixdww1ykujt.fsf@squid.pdc.kth.se>
Lines: 40
X-Mailer: Gnus v5.6.45/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> Here are a few examples:
> 1) Created a file, and it immediately shows up, but it reports "no
> such file or directory" when doing ls. (Same as if you mkm a non-existent
> volume.) Problem is, the file can't be removed or recreated.
This normally works. Could you give a more thorough explanation of
what you do when this happens?
> 2) sigpending lied - I am getting so many of these that it is
> becoming a performance problem. The login time for an AFS account is
> significantly different when these are occurring.
Are they always occuring? I have never seen these.
> 4) Complete lockups and oops's: In some cases, the lockups appear to
> be an extreme case of sigpending lied. In others, they are oopses.
Here is a patch that might work:
Index: xfs_message.c
===================================================================
RCS file: /usr/local/cvsroot/arla/xfs/linux/xfs_message.c,v
retrieving revision 1.46
diff -u -r1.46 xfs_message.c
--- xfs_message.c 1999/01/31 17:21:23 1.46
+++ xfs_message.c 1999/02/04 16:04:34
@@ -284,12 +284,12 @@
XFSDEB(XDEBMSG, ("clear_all_childs: invalidating %p aliases:\n",
child->d_inode));
print_aliases(child->d_inode);
+ DENTRY_TO_XDENTRY(child)->valid = 0;
}
XFSDEB(XDEBMSG, ("clean_all_childs: child->d_count: %d child->d_inode: %p\n",
child->d_count, child->d_inode));
if (child->d_count == 0) /* Throw immediately */
d_drop(child);
- DENTRY_TO_XDENTRY(child)->valid = 0;
}
alias = alias->next;
}
