[825] in arla-drinkers

home help back first fref pref prev next nref lref last post

Failures with arla-0.23

daemon@ATHENA.MIT.EDU (Dr A V Le Blanc)
Thu May 13 08:54:45 1999

From owner-arla-drinkers@stacken.kth.se Thu May 13 12:54:45 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 19661 invoked from network); 13 May 1999 12:54:44 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 13 May 1999 12:54:44 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id OAA23866
	for arla-drinkers-list; Thu, 13 May 1999 14:47:26 +0200 (MET DST)
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id OAA23862
	for <arla-drinkers@stacken.kth.se>; Thu, 13 May 1999 14:47:21 +0200 (MET DST)
Received: from meissen.mcc.ac.uk ([130.88.203.42])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	for arla-drinkers@stacken.kth.se
	id 10hutR-0000Gf-00; Thu, 13 May 1999 13:47:17 +0100
Received: (from zlsiial@localhost)
          by meissen.mcc.ac.uk (8.7.6/8.8.4)
	  id NAA05917 for arla-drinkers@stacken.kth.se; Thu, 13 May 1999 13:47:16 +0100 (BST)
Message-ID: <19990513134716.B5862@afs.mcc.ac.uk>
Date: Thu, 13 May 1999 13:47:16 +0100
From: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
To: arla-drinkers@stacken.kth.se
Subject: Failures with arla-0.23
Reply-To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

I've been having some difficulties with arla-0.23 (on libc6 Linux
systems running various 2.2 kernels) getting into an odd state
in which attempts to access files in /afs more or less always hang
after arla has been active for a day or so.  It can be fixed by
killing arlad, unmounting /afs, rmmoding xfs, and restarting arla.
Has anyone else seen this sort of problem?  I recall some messages
that seemed similar a few weeks ago; it would be nice if this
problem is fixed in 0.24 when it comes out.

     -- Owen
     LeBlanc@mcc.ac.uk

home help back first fref pref prev next nref lref last post