[4129] in arla-drinkers
Re: crash on NetBSD
daemon@ATHENA.MIT.EDU (Tomas Olsson)
Mon Jan 15 08:52:08 2007
From arla-drinkers-bounces@stacken.kth.se Mon Jan 15 13:52:07 2007
Return-Path: <arla-drinkers-bounces@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 5775 invoked from network); 15 Jan 2007 13:52:07 -0000
Received: from mx1.kth.se (130.237.32.140)
by charon.mit.edu with SMTP; 15 Jan 2007 13:52:07 -0000
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx1.kth.se (Postfix) with ESMTP id 1B79F140726;
Mon, 15 Jan 2007 14:52:06 +0100 (CET)
Received: from mx1.kth.se ([127.0.0.1])
by localhost (mx1.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP
id 16216-01-11; Mon, 15 Jan 2007 14:52:03 +0100 (CET)
Received: from tapas.stacken.kth.se (tapas.stacken.kth.se [130.237.234.140])
by mx1.kth.se (Postfix) with ESMTP id 4391E140520;
Mon, 15 Jan 2007 14:52:01 +0100 (CET)
Received: from tapas.stacken.kth.se (localhost [127.0.0.1])
by tapas.stacken.kth.se (Postfix) with ESMTP id 04B2B53515;
Mon, 15 Jan 2007 14:52:00 +0100 (CET)
X-Original-To: arla-drinkers@tapas.stacken.kth.se
Delivered-To: arla-drinkers@tapas.stacken.kth.se
Received: from brev.stacken.kth.se (brev.stacken.kth.se [130.237.234.84])
by tapas.stacken.kth.se (Postfix) with ESMTP id A05FA53515
for <arla-drinkers@tapas.stacken.kth.se>;
Mon, 15 Jan 2007 14:51:59 +0100 (CET)
Received: from mx2.kth.se (mx2.kth.se [130.237.48.98])
by brev.stacken.kth.se (8.12.10/8.12.10) with ESMTP id l0FDpxN6019690
for <arla-drinkers@stacken.kth.se>;
Mon, 15 Jan 2007 14:51:59 +0100 (MET)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mx2.kth.se (Postfix) with ESMTP id EAE6914056F
for <arla-drinkers@stacken.kth.se>;
Mon, 15 Jan 2007 14:51:58 +0100 (CET)
Received: from mx2.kth.se ([127.0.0.1])
by localhost (mx2.kth.se [127.0.0.1]) (amavisd-new,
port 10024) with LMTP
id 16198-01-30; Mon, 15 Jan 2007 14:51:53 +0100 (CET)
Received: from kashyyyk.ite.kth.se (kashyyyk.ite.kth.se [130.237.31.35])
by mx2.kth.se (Postfix) with ESMTP id 3D75014052E;
Mon, 15 Jan 2007 14:51:53 +0100 (CET)
Received: by kashyyyk.ite.kth.se (Postfix, from userid 18404)
id 3467D960140; Mon, 15 Jan 2007 14:51:53 +0100 (CET)
From: Tomas Olsson <tol@it.su.se>
To: "Tracy Di Marco White" <gendalia@gmail.com>
Subject: Re: crash on NetBSD
References: <7024c8c80701130047s39f112f9webef0805f3a3b5dc@mail.gmail.com>
Date: 15 Jan 2007 14:51:53 +0100
In-Reply-To: <7024c8c80701130047s39f112f9webef0805f3a3b5dc@mail.gmail.com>
Message-ID: <lsrtzysgzye.fsf@kashyyyk.ite.kth.se>
Lines: 32
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at kth.se
X-Spam-Status: No, hits=-4.9 tagged_above=-200.0 required=5.0 tests=BAYES_00
X-Spam-Level:
Cc: arla-drinkers@stacken.kth.se
X-BeenThere: arla-drinkers@stacken.kth.se
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: Arla discussions <arla-drinkers.stacken.kth.se>
List-Unsubscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=unsubscribe>
List-Archive: <http://lists.stacken.kth.se/pipermail/arla-drinkers>
List-Post: <mailto:arla-drinkers@stacken.kth.se>
List-Help: <mailto:arla-drinkers-request@stacken.kth.se?subject=help>
List-Subscribe: <https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers>,
<mailto:arla-drinkers-request@stacken.kth.se?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: arla-drinkers-bounces@stacken.kth.se
Errors-To: arla-drinkers-bounces@stacken.kth.se
X-Virus-Scanned: by amavisd-new at kth.se
"Tracy Di Marco White" <gendalia@gmail.com> writes:
> I salvaged several volumes, and the process left hundreds of
> __ORPHANFILE_.#*.#* in the root of the volumes involved. Since that day,
> two of our webservers have started having arla fail. The two machines
> involved are running NetBSD 2.0.2/i386, and both are now running arla
> 0.43.
>
Tricky one. Some random thoughts:
Try checking out arla-0-44-branch from cvs, there are a few changes to
lib/bufdir that may very well be relevant.
I take it that this is not happening every time you access those volumes?
If it happens within some reasonable amount of time (before your disk is
full), you could run arlad with --tracefile=arla.trace (ends up in the
chroot dir) and see if you can see any interesting operations just before
the crash (use nnpfs/readtrace.py).
Are there any modifying operations, like rename or unlink, going on?
Especially cross cell renames.
Maybe some more details from gdb could be interesting, like if the page*
addresses are totally broken, if the fbuf and the directory has the same
idea about size, ... Oh, and look at workers[] (0-15 or so?) to see what
they are doing.
I assume the salvage operation produced coherent and sane volumes,
especially since none of my code was involved ;) But one could run
arla-obj/arlad/afsdir_check (not installed) on directories in the cache,
like 02/2C in your second trace, just to see if they look good.
/t
_______________________________________________
Arla-drinkers mailing list
Arla-drinkers@stacken.kth.se
https://lists.stacken.kth.se/mailman/listinfo/arla-drinkers
