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

New item:

Browse source 
- swapping performance on 6.0 is much worse than on 4.x.

Update items:
 - "unmount pending error": ssouhlal@ is investigating.
 - "quota deadlocks": jeff@ is investigating.
 - "IPv6 panic with date(1)": ume@'s patch seems to address
   this problem and dwmalone@ is working on some other missing
   locking.

Thanks to:	kris
This commit is contained in:
Hiroki Sato 2006-02-14 01:40:16 +00:00
parent 285a5c3e66
commit bbc6534d59
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=27123
1 changed files with 16 additions and 8 deletions

24
en/releases/6.1R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../.."> <!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'> <!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.9 2006/02/11 06:36:55 scottl Exp $"> <!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.10 2006/02/13 21:21:56 brueffer Exp $">
<!ENTITY local.rel "6.1"> <!ENTITY local.rel "6.1">
<!ENTITY title "FreeBSD 6.1 Open Issues"> <!ENTITY title "FreeBSD 6.1 Open Issues">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes; <!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
@ -79,8 +79,8 @@
<tr> <tr>
<td>unmount pending error</td> <td>unmount pending error</td>
<td>&status.unknown;</td> <td>&status.wip;</td>
<td></td> <td>&a.ssouhlal;</td>
<td>When unmounting filesystems &a.kris; reports seeing this warning: <tt>/c: unmount pending error: blocks -68512 files 0</tt>. This dates back at least to 5.3. It might be associated with <td>When unmounting filesystems &a.kris; reports seeing this warning: <tt>/c: unmount pending error: blocks -68512 files 0</tt>. This dates back at least to 5.3. It might be associated with
filesystem corruption reported by many users in which the 'used' space filesystem corruption reported by many users in which the 'used' space
on a filesystem is negative; fsck -f is needed to correct this.</td> on a filesystem is negative; fsck -f is needed to correct this.</td>
@ -103,8 +103,8 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
<tr> <tr>
<td>quota deadlocks</td> <td>quota deadlocks</td>
<td>&status.unknown;</td> <td>&status.wip;</td>
<td></td> <td>&a.jeff;</td>
<td>Quota support is not locked properly and causes deadlocks.</td> <td>Quota support is not locked properly and causes deadlocks.</td>
</tr> </tr>
@ -124,8 +124,8 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
<tr> <tr>
<td>amd64 panics in ipv6 with date(1)</td> <td>amd64 panics in ipv6 with date(1)</td>
<td>&status.unknown;</td> <td>&status.wip;</td>
<td></td> <td>&a.ume; and &a.dwmalone;</td>
<td>amd64 panics in ipv6 when the date is changed using date(1) or <td>amd64 panics in ipv6 when the date is changed using date(1) or
ntpdate(1). This may be a MI issue.</td> ntpdate(1). This may be a MI issue.</td>
</tr> </tr>
@ -309,6 +309,15 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
sys-admins tend to do.</td> sys-admins tend to do.</td>
</tr> </tr>
<tr>
<td>swapping on 6.0 is slower than on 4.x</td>
<td>&status.new;</td>
<td>&nbsp;</td>
<td>Performance on swap handling is much slower than 4.x and
this can make a system essentially unusable when moderate
paging activity is going on.</td>
</tr>
</table> </table>
<h3>Documentation items that must be resolved for &local.rel;</h3> <h3>Documentation items that must be resolved for &local.rel;</h3>
@ -324,7 +333,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
</table> </table>
<h3>Testing foci for &local.rel;-RELEASE</h3> <h3>Testing foci for &local.rel;-RELEASE</h3>
<a name="testing"></a> <a name="testing"></a>