[306] in arla-drinkers

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

file corruption with arla

daemon@ATHENA.MIT.EDU (Jim Nance)
Mon Oct 5 16:24:03 1998

From owner-arla-drinkers@stacken.kth.se Mon Oct 05 20:24:03 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 19002 invoked from network); 5 Oct 1998 20:24:02 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
  by bloom-picayune.mit.edu with SMTP; 5 Oct 1998 20:24:02 -0000
Received: (from majordom@localhost)
	by sundance.stacken.kth.se (8.8.8/8.8.8) id WAA10143
	for arla-drinkers-list; Mon, 5 Oct 1998 22:18:19 +0200 (MET DST)
Received: from sailboat.acs.uncwil.edu (sailboat.acs.uncwil.edu [152.20.10.11])
	by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id WAA10139
	for <arla-drinkers@stacken.kth.se>; Mon, 5 Oct 1998 22:18:15 +0200 (MET DST)
Received: (from jim@localhost)
	by sailboat.acs.uncwil.edu (8.8.7/8.8.7) id QAA29380;
	Mon, 5 Oct 1998 16:19:00 -0400
Message-ID: <19981005161859.11285@sailboat.acs.uncwil.edu>
Date: Mon, 5 Oct 1998 16:18:59 -0400
From: Jim Nance <jim@sailboat.acs.uncwil.edu>
To: arla-drinkers@stacken.kth.se
Subject: file corruption with arla
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85e
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk

Hello All,
    I have been playing around with arla for a couple of months.  Overall,
I am very pleased/impressed with the software.  Unfortunately I do have
a problem to report.  What happens is that when I build software in an
AFS directory tree I will eventually get corrupt files in the cache.  Doing
an fs flushv path_to_file will uncorrupt the file.  The file and length of
time it takes to become corrupt is random, but I can never get through a
large build successfully because something will always get corrupted.
    I initially assumed that the contents of the file were just trash, but
I looked a little harder today.  It seems that the bad files actually
contain good copies of other files.  Its like the mapping of cached file
to cached file name has become corrupt.  I have seen this problem with
several versions of arla and several versions of the 2.1.X linux kernel.
My current configuration is Red Hat 5.1+updates, linux 2.1.124, and
arla-0.13.
	If anyone would like more information, please let me know.

Thanks,

Jim

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