[475] in arla-drinkers
Arla /afs won't come up unless cache is first nuked.
daemon@ATHENA.MIT.EDU (Werner Krebs)
Sat Jan 9 19:57:52 1999
From owner-arla-drinkers@stacken.kth.se Sun Jan 10 00:57:50 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 2269 invoked from network); 10 Jan 1999 00:57:48 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 10 Jan 1999 00:57:48 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id BAA23547
for arla-drinkers-list; Sun, 10 Jan 1999 01:53:22 +0100 (MET)
Received: from csbgly.csb.yale.edu (csbgly.csb.yale.edu [130.132.17.43])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id BAA23541
for <arla-drinkers@stacken.kth.se>; Sun, 10 Jan 1999 01:53:18 +0100 (MET)
Received: from csbmet.csb.yale.edu (csbmet [130.132.17.44])
by csbgly.csb.yale.edu (8.9.1a/8.9.1) with ESMTP id TAA13793
for <arla-drinkers@stacken.kth.se>; Sat, 9 Jan 1999 19:53:16 -0500 (EST)
Received: from bofur.csb.yale.edu (bofur.csb.yale.edu [130.132.17.176]) by csbmet.csb.yale.edu (8.6.11/8.6.11) with ESMTP id TAA15702 for <arla-drinkers@stacken.kth.se>; Sat, 9 Jan 1999 19:53:15 -0500
Received: from oin.csb.yale.edu (net186-119.its.yale.edu [130.132.186.119])
by bofur.csb.yale.edu (8.8.7/8.8.5) with SMTP id TAA04661
for <arla-drinkers@stacken.kth.se>; Sat, 9 Jan 1999 19:53:45 -0500
Message-ID: <3697FC14.48AA@yale.edu>
Date: Sat, 09 Jan 1999 20:02:12 -0500
From: Werner Krebs <werner.krebs@yale.edu>
Organization: Yale University
X-Mailer: Mozilla 3.01Gold (Win95; U)
MIME-Version: 1.0
To: arla-drinkers@stacken.kth.se
Subject: Arla /afs won't come up unless cache is first nuked.
References: <19990108212754.11913.rocketmail@send203.yahoomail.com> <ixdvhigrmsv.fsf@scup.pdc.kth.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
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.
This happens everytime the machine is rebooted, or arla is simply
sent a -TERM.
The solution is to put an rm -rf $CACHE in /etc/init.d/arla.
Cache building is fairly quick (unlike one installation of
commercial AFS, where it took over 15 minutes for 150 meg cache, and
nothing else could run or you risked a kernel panic), so this isn't that
big of a deal, and this makes arla reliable.
