From owner-cvs-all Fri Feb 8 2:50:39 2002 Delivered-To: cvs-all@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BCBB937B419; Fri, 8 Feb 2002 02:50:36 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id A93825341; Fri, 8 Feb 2002 11:50:34 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Kirk McKusick Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_alloc.c References: <200202072213.g17MDuW98705@freefall.freebsd.org> From: Dag-Erling Smorgrav Date: 08 Feb 2002 11:50:34 +0100 In-Reply-To: <200202072213.g17MDuW98705@freefall.freebsd.org> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kirk McKusick writes: > Log: > Occationally background fsck would cause a spurious ``freeing free > inode'' panic. This change corrects that problem by setting the > fs_active flag when the inode map changes to notify the snapshot > code that the cylinder group must be rescanned. BTW - not really related to this, but I occasionally get "mount pending errors" when I mount a filesystem that has just gone through 'fsck -y' after a crash. I don't use background fsck, so I shouldn't ever get "mount pending errors", and especially not on a (presumably) clean filesystem! DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message