Date: Fri, 25 Feb 2000 08:18:20 +0100 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Matt Dillon <dillon@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_balloc.c Message-ID: <20000225081820.Q79013@daemon.ninth-circle.org> In-Reply-To: <200002242043.MAA17349@freefall.freebsd.org>; from dillon@FreeBSD.org on Thu, Feb 24, 2000 at 12:43:22PM -0800 References: <200002242043.MAA17349@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-On [20000225 00:00], Matt Dillon (dillon@FreeBSD.org) wrote: > Fix a 'freeing free block' panic in UFS. The problem occurs when the > filesystem fills up. If the first indirect block exists and FFS is able > to allocate deeper indirect blocks, but is not able to allocate the > data block, FFS improperly unwinds the indirect blocks and leaves a > block pointer hanging to a freed block. This will cause a panic later > when the file is removed. The solution is to properly account for the > first block-pointer-to-an-indirect-block we had to create in a balloc > operation and then unwind it if a failure occurs. I will update my newshub with the latest sources again and see if I get the ffs panics again. JFYI, the box hasn't paniced in over 35 hours now, so the panics do seem to be panics and not faulty hardware. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; When we have not what we like, we must like what we have... 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?20000225081820.Q79013>