From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 07:30:12 2004 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 9E27616A4CE for ; Mon, 29 Nov 2004 07:30:12 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8620B43D48 for ; Mon, 29 Nov 2004 07:30:12 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 76D8A72DF8; Sun, 28 Nov 2004 23:30:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 72BD872DD4; Sun, 28 Nov 2004 23:30:12 -0800 (PST) Date: Sun, 28 Nov 2004 23:30:12 -0800 (PST) From: Doug White To: Paul Mather In-Reply-To: <1101228017.38787.12.camel@gromit.dlib.vt.edu> Message-ID: <20041128232435.X40277@carver.gumbysoft.com> References: <1101228017.38787.12.camel@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Mount pending error? 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, 29 Nov 2004 07:30:12 -0000 On Tue, 23 Nov 2004, Paul Mather wrote: > Last night, this appeared in my logs (and on my console): > > Nov 23 03:05:36 zappa kernel: /data: mount pending error: blocks -1696 files 0 > > > What is a "mount pending error?" I have heard this in conjunction with > unclean shutdowns and fsck, but my system was not shut down recently, > nor has /data (on a geom_stripe) been unmounted (cleanly or otherwise). > > The only thing I have done that could be related is to make a snapshot > (later removed), but it was not of the filesystem being complained > about. (Also, I create and mount snapshots of all my filesystems as > part of my nightly TSM backup.) > > I guess I should shutdown and fsck just to make certain everything is > okay. I am puzzled why this happened, though. (I've been running the > backups for a while, and have not had any complaints.) Looking at the code in ffs_mountfs(), this is data pulled straight from the superblock, so I think its some recordkeeping that softupdates is doing. Immediately after reading those fields they are zeroed so I think its information on where softupdates was at when the filesystem (or snapshot) was mounted. Obviously if there are outstanding softupdate ops when the snapshot is taken it may not be including those in the snap. AFAIK its harmless. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org