From owner-freebsd-current@FreeBSD.ORG Sat Jan 28 00:53:10 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 4B1C116A420 for ; Sat, 28 Jan 2006 00:53:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BCC643D48 for ; Sat, 28 Jan 2006 00:53:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D70451A3C1D; Fri, 27 Jan 2006 16:53:09 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 679E1520B2; Fri, 27 Jan 2006 19:53:05 -0500 (EST) Date: Fri, 27 Jan 2006 19:53:04 -0500 From: Kris Kennaway To: Chuck Swiger Message-ID: <20060128005304.GA70164@xor.obsecurity.org> References: <20060128000909.GA69458@xor.obsecurity.org> <43DABFCA.5030509@mac.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <43DABFCA.5030509@mac.com> 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 00:53:10 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 27, 2006 at 07:50:18PM -0500, Chuck Swiger wrote: > Kris Kennaway wrote: > > /c: unmount pending error: blocks -68512 files 0 =20 > >=20 > > This warning has been popping up sporadically on my systems at reboot > > time since FreeBSD 5.3..what causes it? >=20 > 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. Kris > > % find /usr/src/sys -name *.c -print0 | xargs -0 grep -n 'unmount pendi= ng error:' > /usr/src/sys/ufs/ffs/ffs_vfsops.c:961: >=20 > if (fs->fs_pendingblocks !=3D 0 || fs->fs_pendinginodes !=3D 0) { > printf("%s: unmount pending error: blocks %jd files %d\n", > fs->fs_fsmnt, (intmax_t)fs->fs_pendingblocks, > fs->fs_pendinginodes); > fs->fs_pendingblocks =3D 0; > fs->fs_pendinginodes =3D 0; > } >=20 > A quick look there suggests that ffs_unmount() tries to call > softdep_flushfiles() or ffs_flushfiles(). Apparently, if those fail to f= lush > all pending data, the error message you've seen is generated. >=20 > The printf() statement should be using an unsigned int format string rath= er than > claiming a negative number of blocks is affected, or perhaps > fs->fs_pendingblocks ought to be an u_int64_t...? >=20 > --=20 > -Chuck >=20 --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD2sBwWry0BWjoQKURAkErAJ9sZQwZUdCyD5YgEJtAAHMVT30+rQCg9qr2 P94s/2khAFFWNzbTO32jc2Q= =ssZo -----END PGP SIGNATURE----- --5vNYLRcllDrimb99--