From owner-freebsd-current@FreeBSD.ORG Sat Jan 28 03:45:43 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 8A8AF16A420 for ; Sat, 28 Jan 2006 03:45:43 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8123343D53 for ; Sat, 28 Jan 2006 03:45:42 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 0A3962ACCF; Fri, 27 Jan 2006 21:45:41 -0600 (CST) Date: Fri, 27 Jan 2006 21:45:39 -0600 From: Craig Boston To: "Matthew D. Fuller" Message-ID: <20060128034539.GA44075@nowhere> Mail-Followup-To: Craig Boston , "Matthew D. Fuller" , Kris Kennaway , current@FreeBSD.org References: <20060128000909.GA69458@xor.obsecurity.org> <43DABFCA.5030509@mac.com> <20060128005304.GA70164@xor.obsecurity.org> <20060128013955.GH1388@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060128013955.GH1388@over-yonder.net> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org, Kris Kennaway 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 03:45:43 -0000 On Fri, Jan 27, 2006 at 07:39:55PM -0600, Matthew D. Fuller wrote: > 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. I've been seeing this as well -- on a system with flash memory for its configuration (/config). /etc is a malloc-backed md. Periodically a script runs that compares /etc to /config; if any changes are detected /config is remounted read-write and the changes sycned over, then it is remounted read-only (all done with mount -u). This way power can be cut at any time with a very low risk of the filesystems being dirty. When I moved it from 5.x to 6.x I started seeing the "update error" messages when it was remounted read-only, and if I ran fsck it would find problems. I ended up having to modify the script to unmount /config completely and then mount it read-only... I don't think it's quite the same as Kris's problem though as I've never seen it with a negative number. Craig