Date: Sun, 10 Feb 2002 22:50:15 -0800 From: Kirk McKusick <mckusick@mckusick.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_alloc.c Message-ID: <200202110650.g1B6oFi07216@beastie.mckusick.com> In-Reply-To: Your message of "08 Feb 2002 11:50:34 %2B0100." <xzpaduk9rid.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
To: Kirk McKusick <mckusick@FreeBSD.org> 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 <des@ofug.org> Date: 08 Feb 2002 11:50:34 +0100 Kirk McKusick <mckusick@FreeBSD.org> 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 The above fix should make your problem go away. Note that you will get the mount pending error if you mount a dirty filesystem (e.g., one that is later cleaned up by fsck). Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202110650.g1B6oFi07216>