[478] in arla-drinkers
Re: Arla /afs won't come up unless cache is first nuked.
daemon@ATHENA.MIT.EDU (Brandon S. Allbery KF8NH)
Sat Jan 9 20:34:28 1999
From owner-arla-drinkers@stacken.kth.se Sun Jan 10 01:34:26 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 2608 invoked from network); 10 Jan 1999 01:34:25 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 10 Jan 1999 01:34:25 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id CAA23949
for arla-drinkers-list; Sun, 10 Jan 1999 02:30:06 +0100 (MET)
Received: from hilfy.ece.cmu.edu (root@HILFY.ECE.CMU.EDU [128.2.253.106])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id CAA23934
for <arla-drinkers@stacken.kth.se>; Sun, 10 Jan 1999 02:30:00 +0100 (MET)
Received: from speaker.kf8nh.apk.net (root@ANNEX-3.SLIP.ECE.CMU.EDU [128.2.236.3])
by hilfy.ece.cmu.edu (8.8.8/8.8.8) with ESMTP id UAA00862
for <arla-drinkers@stacken.kth.se>; Sat, 9 Jan 1999 20:30:03 -0500 (EST)
Received: from rushlight.kf8nh.apk.net (allbery@rushlight.kf8nh.apk.net [10.9.204.1])
by speaker.kf8nh.apk.net (8.8.7/8.8.7) with ESMTP id UAA09191
for <arla-drinkers@stacken.kth.se>; Sat, 9 Jan 1999 20:29:56 -0500
Received: (from allbery@localhost)
by rushlight.kf8nh.apk.net (8.8.7/8.8.7) id UAA05624;
Sat, 9 Jan 1999 20:29:54 -0500
Message-Id: <199901100129.UAA05624@rushlight.kf8nh.apk.net>
X-Mailer: exmh version 2.0.2 2/24/98
To: arla-drinkers@stacken.kth.se
Subject: Re: Arla /afs won't come up unless cache is first nuked.
In-reply-to: Your message of "Sat, 09 Jan 1999 20:02:12 EST."
<3697FC14.48AA@yale.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 09 Jan 1999 20:29:54 -0500
From: "Brandon S. Allbery KF8NH" <allbery@kf8nh.apk.net>
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
In message <3697FC14.48AA@yale.edu>, Werner Krebs writes:
+-----
| Arla on my RedHat 5.2 box running 2.0.36 needs to have its cache
| nuked or it won't come up properly (shows nothing when an 'ls' is
| done in /afs). If arlad is killed and the cache is nuked, /afs
| comes up fine the next time arlad is restarted.
+--->8
FWIW we *sometimes* experience this on 2.1 series kernels (various 2.1.125 -
2.1.131). Not always. And it's not always root.afs that is messed up ---
once it was root.cell (/afs/ece.cmu.edu).
It doesn't happen often enough to be a show-stopper; arlad getting confused
about which volume's cache it is searching (mentioned in a previous note a
few wweks ago) is more common.
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.
