From owner-freebsd-current@FreeBSD.ORG  Thu Jul  8 09:26:57 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D493516A4CE; Thu,  8 Jul 2004 09:26:57 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 91BEB43D45; Thu,  8 Jul 2004 09:26:57 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i689QeS0008918;
	Thu, 8 Jul 2004 02:26:44 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200407080926.i689QeS0008918@gw.catspoiler.org>
Date: Thu, 8 Jul 2004 02:26:40 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: mich@FreeBSD.org
In-Reply-To: <20040708091051.GC50232@mich2.itxmarket.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: glebius@cell.sick.ru
cc: current@FreeBSD.org
Subject: Re: today's CURRENT lockups
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2004 09:26:57 -0000

On  8 Jul, Michael L. Hostbaek wrote:
> Don Lewis (truckman) writes:
>> 
>> I got bit by this problem when I tried to do some browsing on my
>> Thinkpad R40 after my primary (4.10-STABLE) machine lost a disk.
>> 
>> It's a July 5th kernel with SCHED_ULE, DDB, INVARIANTS, WITNESS, and
>> ACPI.
> 
> Try to cvsup your sources, and rebuild your kernel. rwatson's commit to
> sched_ule.c (rev. 1.113) fix this issue for me.

I use cvsup in CVS mode maintain a local copy of the repository, and
then use cvs to update the local machines from that repository.  My copy
of the cvs repository lived on the dead disk.  I fired up mozilla on my
laptop to go shopping for a replacement disk ...

  There's a hole in the bucket, dear Liza, dear Liza
  There's a hole in the bucket, dear Liza, there's a hole.

I was able to salvage all the data and scrounged up a couple of
replacement disks, and when I loaded the data onto the new disks it
became apparent that there are some severe performace problems in the
filesystem code, probably in the inode and/or block allocators.
Restoring 5 GB of data to the cyrus imap spool directory that was also
on that disk took about 6 hours ...