Date: Thu, 29 Nov 2007 19:27:50 -0500 From: Bill Vermillion <bv@wjv.com> To: David Cecil <david.cecil@nokia.com> Cc: freebsd-fs@freebsd.org Subject: Re: File remove problem Message-ID: <20071130002750.GA36329@wjv.com> In-Reply-To: <474F4E46.8030109@nokia.com> References: <474F4E46.8030109@nokia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 30, 2007 at 09:41 David Cecil saw "Error reading FAT table? Try SKINNY table?" And promptly said: > Hi, > I've been looking into a problem we're seeing on FreeBSD 6.1, though I > believe the bug will exist in current, or at least 7.0. > Under certain circumstances, when a file is > removed from the filesystem, and the filesystem > is remounted read-only immediately afterwards, > an error such as the following is displayed: > g_vfs_done():mirror/gmroots1f[WRITE(offset=1349058560, > length=16384)]error = 1 > I have determined that the buffer contains an update to the > inode for the file that's deleted. The inode for the directory > change appears to be updated correctly. So what's not making it > to disk is the updated file inode with its changed link counts > (should now be zero). So, somehow this inode is being missed > during the sync prior to the remount completing. > I'm still looking through the code to find the problem, but any > insights from those more familiar with the code would be much > appreciated. Are you sure the sync occured? What happens if you run 'sync' and then perform the above process? Bill -- Bill Vermillion - bv @ wjv . com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071130002750.GA36329>