os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move the Vinum item to the 'test' section.

Browse source
This commit is contained in:
Scott Long 2003-11-23 17:38:41 +00:00
parent a80737415b
commit 52aba80ff3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=18961
1 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

30
en/releases/5.2R/todo.sgml
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.2R/todo.sgml,v 1.61 2003/11/21 02:10:30 scottl Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.2R/todo.sgml,v 1.62 2003/11/21 02:16:13 scottl Exp $">
<!ENTITY title "FreeBSD 5.2 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -77,20 +77,6 @@
reliable reproduction scenario.</td>
</tr>
<tr>
<td>Vinum data corruption and memory allocation problems</td>
<td>&status.wip;</td>
<td>&nbsp;</td>
<td>In the last week, reports of two new (and possibly related)
Vinum failures have come to light: a warning message of
<code>vinum: exiting with malloc table inconsistency at
0xc2053c00 from vinumio.c:755</code> has been experienced when
Vinum auto-configuration fails. Also, even simple test cases
for Vinum I/O appear to result in incorrect data being returned
from disk, rendering Vinum unusable in several reproduceable
configurations.</td>
</tr>
</table>
<h3>Required features for 5.2-RELEASE</h3>
@ -456,6 +442,20 @@
beta.</td>
</tr>
<tr>
<td>Vinum data corruption and memory allocation problems</td>
<td>&status.untested;</td>
<td>&a.grog;</td>
<td>In the last week, reports of two new (and possibly related)
Vinum failures have come to light: a warning message of
<code>vinum: exiting with malloc table inconsistency at
0xc2053c00 from vinumio.c:755</code> has been experienced when
Vinum auto-configuration fails. Also, even simple test cases
for Vinum I/O appear to result in incorrect data being returned
from disk, rendering Vinum unusable in several reproduceable
configurations.</td>
</tr>
</table>
&footer;