From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 23:32:45 2003 Return-Path: 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 269D237B401; Sat, 12 Jul 2003 23:32:45 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8522943FA3; Sat, 12 Jul 2003 23:32:44 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h6D6WaM7024179; Sat, 12 Jul 2003 23:32:39 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200307130632.h6D6WaM7024179@gw.catspoiler.org> Date: Sat, 12 Jul 2003 23:32:36 -0700 (PDT) From: Don Lewis To: jeff@walters.name In-Reply-To: <200307130004.41123.jeff@walters.name> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: smkelly@FreeBSD.org cc: current@FreeBSD.org Subject: Re: sporadic disk syncing failures when shutting down X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 06:32:45 -0000 On 13 Jul, Jeff Walters wrote: > On Saturday 12 July 2003 11:24 pm, Sean Kelly wrote: > >> > syncing disks, buffers remaining... 54 54 54 54 54 54 54 54 54 54 54 54 >> > 54 54 54 54 54 54 54 54 giving up on 54 buffers >> > Uptime: 6m42s >> > Terminate ACPI >> > Rebooting... >> > >> > Each time this has happened, fsck finds and nukes a bunch of empty >> > directories. The last time this happened, the /etc/rc.d/yp* files that >> > mergmaster updated were missing after the reboot and fsck had done its >> > work. Nothing has ever shown up in lost+found. >> > >> > Has anyone else seen this? >> >> I have seen this a lot, but not as much lately. Sadly, I don't have any >> more data than you on why it happens. I've seen it give up on a rather >> frighteningly large number of buffers before, though... > > I hate to even mentioned such an unscientific observation where I made > multiple changes at once, but I'll provide a data point. I also saw this > problem crop up at the same time as I tried the SCHED_ULE scheduler a couple > of months ago. I re-cvsup'ed CURRENT and switched back to SCHED_4BSD and it > went away. I haven't gotten around to trying anything other than SCHED_4BSD.