The ffs_blkfree panic has been resolved, with no further reports.

Trim from the testing list.
This commit is contained in:
Robert Watson 2003-05-16 21:18:40 +00:00
parent 51d42a45e3
commit 8aef21962b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16926

View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.47 2003/05/16 21:16:32 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.1R/todo.sgml,v 1.48 2003/05/16 21:17:24 rwatson Exp $">
<!ENTITY title "FreeBSD 5.1 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -273,22 +273,6 @@
This change has been committed, and requires broader testing.</td>
</tr>
<tr>
<td>panic: ffs_blkfree</td>
<td>Patch committed</td>
<td>&a.alc;</td>
<td>Starting in late April, reports of a new UFS panic,
"panic: ffs_blkfree: freeing free frag" began to pop up with
a high frequency in some environments. This problem appears
to have been associated with a bug introduced in the VM system
that has now been resolved. Users who updated to a kernel
between approximately May 1 and May 4 will want to run a full
foreground fsck on all file systems to make sure that no
remaining free space accounting errors exist. However, we
should be on the lookout for any recurrence of this problem
due to its serious nature.</td>
</tr>
<tr>
<td>TIMEWAIT panic for network labeled MAC policy modules</td>
<td>Patch committed</td>