[312] in arla-drinkers
freebsd 2.2.5 and arla-0.13
daemon@ATHENA.MIT.EDU (Eric Hoffman)
Tue Oct 6 18:59:29 1998
From owner-arla-drinkers@stacken.kth.se Tue Oct 06 22:59:28 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 10425 invoked from network); 6 Oct 1998 22:59:27 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 6 Oct 1998 22:59:27 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id AAA01344
for arla-drinkers-list; Wed, 7 Oct 1998 00:53:24 +0200 (MET DST)
Received: from tesuji.cs.washington.edu (tesuji.cs.washington.edu [128.95.2.82])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id AAA01338
for <arla-drinkers@stacken.kth.se>; Wed, 7 Oct 1998 00:53:20 +0200 (MET DST)
Received: (from hoffman@localhost)
by tesuji.cs.washington.edu (8.8.7/8.8.7) id PAA00492;
Tue, 6 Oct 1998 15:53:18 -0700 (PDT)
(envelope-from hoffman)
Date: Tue, 6 Oct 1998 15:53:18 -0700 (PDT)
Message-Id: <199810062253.PAA00492@tesuji.cs.washington.edu>
From: Eric Hoffman <hoffman@cs.washington.edu>
To: arla-drinkers@stacken.kth.se
Subject: freebsd 2.2.5 and arla-0.13
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
after doing build and install, it took a while to build the cache, but
after I was sure that it was finished, the disk kept on churning...I
ran arlad under gdb, and turned on logging flag -1, and it was
spinning on upcalls from xfs.
Tue Oct 6 15:43:50 1998: arlad: Rec message: opcode = 8 (getdata), size = 40
Tue Oct 6 15:43:50 1998: arlad: Multi-send: opcode = 9 (installdata), size = 452
Tue Oct 6 15:43:50 1998: arlad: multi-sending wakeup: seq = 327023, error = 0
Tue Oct 6 15:43:50 1998: arlad: Rec message: opcode = 8 (getdata), size = 40
Tue Oct 6 15:43:50 1998: arlad: Multi-send: opcode = 9 (installdata), size = 452
Tue Oct 6 15:43:50 1998: arlad: multi-sending wakeup: seq = 327024, error = 0
...
this happens any time I try to stat/readdir/read anthing in the
mounted directory. the 'arlad -t' process level client seems to work
perfectly well for me
the arla project is such a great contribution, I'm quite willing to
spend some time tracking this and similar problems down...if you have
any hints, I'd love to hear from you, otherwise I'll just continue to
try to debug things myself, and let you know should I find anything
thanks for all your work
