From owner-freebsd-current@FreeBSD.ORG Sat Jan 28 01:39:58 2006 Return-Path: X-Original-To: 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 6CCED16A420 for ; Sat, 28 Jan 2006 01:39:58 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3FC743D45 for ; Sat, 28 Jan 2006 01:39:57 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id B1F86AD; Fri, 27 Jan 2006 19:39:56 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id A471061C38; Fri, 27 Jan 2006 19:39:55 -0600 (CST) Date: Fri, 27 Jan 2006 19:39:55 -0600 From: "Matthew D. Fuller" To: Kris Kennaway Message-ID: <20060128013955.GH1388@over-yonder.net> References: <20060128000909.GA69458@xor.obsecurity.org> <43DABFCA.5030509@mac.com> <20060128005304.GA70164@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060128005304.GA70164@xor.obsecurity.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: current@FreeBSD.org Subject: Re: /c: unmount pending error: blocks -68512 files 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 28 Jan 2006 01:39:58 -0000 On Fri, Jan 27, 2006 at 07:53:04PM -0500 I heard the voice of Kris Kennaway, and lo! it spake thus: > On Fri, Jan 27, 2006 at 07:50:18PM -0500, Chuck Swiger wrote: > > Kris Kennaway wrote: > > > /c: unmount pending error: blocks -68512 files 0 > > > > Did you have any processes stuck in an uninterruptable condition > > when you unmounted the filesystem? The message is from: > > Perhaps, but none that I noticed this time. I do encounter that > sometimes though. I have most of my fs's mounted read-only (including things like / and /usr/ports and such) which I'm often mount -u'ing to r/w and back. I see a similar error often ("kernel: /: update error: blocks 20 files 1" is the most recent I see in messages)if I don't take special care to sync sync sync and/or wait a while after using it before mount -u'ing it. It's been happening for a while, back to even before mount -u started blowing up with EFAULT. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.