[735] in arla-drinkers
Re: problem with fstat()
daemon@ATHENA.MIT.EDU (Love)
Wed Mar 31 16:53:19 1999
From owner-arla-drinkers@stacken.kth.se Wed Mar 31 21:53:19 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 24419 invoked from network); 31 Mar 1999 21:53:17 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 31 Mar 1999 21:53:17 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id XAA06136
for arla-drinkers-list; Wed, 31 Mar 1999 23:43:53 +0200 (MET DST)
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id XAA06129
for <arla-drinkers@stacken.kth.se>; Wed, 31 Mar 1999 23:43:49 +0200 (MET DST)
Received: from anchor.s3.kth.se (anchor.s3.kth.se [130.237.43.59])
by elixir.e.kth.se (8.9.2/8.9.2) with ESMTP id XAA20884;
Wed, 31 Mar 1999 23:42:26 +0200 (MET DST)
Received: (from lha@localhost)
by anchor.s3.kth.se (8.9.2/8.9.2) id XAA08279;
Wed, 31 Mar 1999 23:42:25 +0200 (MET DST)
From: Love <lha@stacken.kth.se>
To: A stranger without a name <tyme@dreams.res.cmu.edu>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: problem with fstat()
References: <Pine.LNX.4.10.9903311315320.32322-100000@dreams.res.cmu.edu>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 31 Mar 1999 23:42:25 +0200
In-Reply-To: A stranger without a name's message of Wed, 31 Mar 1999 13:26:28 -0500 (EST)
Message-ID: <amaewttjy6.fsf@anchor.s3.kth.se>
Lines: 31
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
A stranger without a name <tyme@dreams.res.cmu.edu> writes:
A stranger without a name <tyme@dreams.res.cmu.edu> writes:
> There seems to be a problem with whatever arla does when fstat() is called
> with a file on an AFS mount. I've tried changing the settings in
> arla.conf, and an fstat() call in ls keeps hanging on various files... it
> seems a lower fpriority lets it get farther through the dir's file list
> before it freezes, or at least changes the file fstat() hangs on, and
> sometimes it gets through an entire directory with no problem.
Fpriority is (should) be used for disconnected operations (to know what
files are important to keep in the cache). In connected mode I guess it
should allways be 100.
> The hangs are consistant (hangs on the same file or doesn't hang on any
> files in a directory) based on the settings in arla.conf, and maybe only
> on the fpriority setting.
Do you have an example on where the thing hangs ? I tried to some links in
directory (1000+) and it seamed to work. Where does it hang in arlad ?
Guess you have to point a condition breakpoint on the right spot to find it.
What OS, OS version, and architecture ?
> If a 'ls' hangs on file blah, doing a ls blah or ls -l blah also hangs. I
> haven't checked the arla code to see where it could be getting stuck.
Sorry, cant trigger it.
Love
