[572] in arla-drinkers
RE: frequent cache corruption with arla 0.21 on linux 2.2.1
daemon@ATHENA.MIT.EDU (Neulinger, Nathan R.)
Thu Feb 4 11:44:30 1999
From owner-arla-drinkers@stacken.kth.se Thu Feb 04 16:44:30 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 20984 invoked from network); 4 Feb 1999 16:44:29 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 4 Feb 1999 16:44:29 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA01295
for arla-drinkers-list; Thu, 4 Feb 1999 17:39:30 +0100 (MET)
Received: from umr.edu (hermes.cc.umr.edu [131.151.1.68])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA01291;
Thu, 4 Feb 1999 17:39:22 +0100 (MET)
Received: from umr-mail01.cc.umr.edu (umr-mail01.cc.umr.edu [131.151.37.121]) via ESMTP by hermes.cc.umr.edu (8.8.7/R.4.20) id KAA25365; Thu, 4 Feb 1999 10:39:20 -0600 (CST)
Received: by umr-mail01.cc.umr.edu with Internet Mail Service (5.5.2232.9)
id <D9V035MY>; Thu, 4 Feb 1999 10:39:20 -0600
Message-ID: <9DA8D24B915BD1118911006094516EAF019C7ECD@umr-mail02.cc.umr.edu>
From: "Neulinger, Nathan R." <nneul@umr.edu>
To: "'Magnus Ahltorp'" <map@stacken.kth.se>
Cc: arla-drinkers@stacken.kth.se
Subject: RE: frequent cache corruption with arla 0.21 on linux 2.2.1
Date: Thu, 4 Feb 1999 10:39:19 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
charset="ISO-8859-1"
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?
Not sure... I'll try and pay a bit more attention next time. But basically,
I create a file in some fashion, and then right afterwards, the file is
there, but innaccessible.
I think around that time, arlad often goes a bit haywire. I can't flushv or
anything. (Does arla support flushv/checkv?) I'm not positive about this
though.
> > 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.
TONS of them. I _always_ get one of them when starting arlad, and then
usually get them in bursts whenever doing afs accesses - logins or file
copies, etc.
Feb 4 10:14:35 infinity telnetd[624]: connect from falcon.cc.umr.edu
Feb 4 10:14:37 infinity login: nneul login on ttyp1 from falcon.cc.umr.edu
Feb 4 10:14:37 infinity kernel: SIG: sigpending lied
Feb 4 10:14:38 infinity last message repeated 68 times
Feb 4 10:14:46 infinity telnetd[656]: connect from falcon.cc.umr.edu
Feb 4 10:14:46 infinity login: ROOT LOGIN ttyp1 FROM falcon.cc.umr.edu
Feb 4 10:14:46 infinity kernel: SIG: sigpending lied
Feb 4 10:14:47 infinity last message repeated 48 times
Feb 4 10:14:53 infinity telnetd[678]: connect from falcon.cc.umr.edu
Feb 4 10:14:54 infinity login: unixdb login on ttyp1 from falcon.cc.umr.edu
Feb 4 10:14:54 infinity kernel: SIG: sigpending lied
Feb 4 10:14:56 infinity last message repeated 53 times
> > 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:
>
Will apply and let you know.
You don't perhaps have anon-cvs set up do you? Or is your arla cvs
repository in AFS (i.e. can it be mirrored)
-- Nathan
