From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 18:19:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE28F16A4CE for ; Mon, 25 Apr 2005 18:19:03 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F93143D53 for ; Mon, 25 Apr 2005 18:19:03 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 7324969A21; Mon, 25 Apr 2005 14:19:02 -0400 (EDT) Date: Mon, 25 Apr 2005 14:19:00 -0400 From: Bill Moran To: Kris Kennaway Message-Id: <20050425141900.363bca66.wmoran@potentialtech.com> In-Reply-To: <20050425181329.GA41455@xor.obsecurity.org> References: <426BA8FA.3080602@samsco.org> <426BAAE4.1040606@incubus.de> <17005.12955.757773.350868@roam.psg.com> <20050425181329.GA41455@xor.obsecurity.org> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: background_fsck=no does not work? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2005 18:19:03 -0000 Kris Kennaway wrote: > On Mon, Apr 25, 2005 at 08:10:35AM -1000, Randy Bush wrote: > > >> not always be clean. Softupdates (hopefully) means that it will be > > >> consistent and recoverable, but what you're seeing here is normal and > > > Why "hopefully"? Aren't people convinced that it works correctly? > > > > i am convinced, but some of the hosts seem not to be :-) > > > > i see shutdowns which 0 0 0 0 and then shut, and when restarted > > single user and fscked manually show errors. though i think this > > may be in current, which is on most of my hosts. > > Yeah, others have reported this problem on -current, but 5.x does not > have it. Actually, I have seen a similar problem on 5.x WRT OpenOffice ... 0. OpenOffice hangs and cant' be killed 1. Reboot system 2. System claims all buffers flushed, then just hangs 3. After hardbooting, filesystems need fscked I noticed others with similar complaints about OpenOffice, so I haven't said much. The problem also happens pretty rarely, and I don't have any idea how to reproduce it on demand. I don't think this is _quite_ the same problem, however. -- Bill Moran Potential Technologies http://www.potentialtech.com