mention some of the other known severe wapbl problems
This commit is contained in:
parent
25d58d24b2
commit
6c5f250fa0
|
@ -1,4 +1,4 @@
|
|||
$NetBSD: storage,v 1.12 2016/05/01 20:51:36 dholland Exp $
|
||||
$NetBSD: storage,v 1.13 2016/05/05 06:17:45 dholland Exp $
|
||||
|
||||
NetBSD Storage Roadmap
|
||||
======================
|
||||
|
@ -90,7 +90,10 @@ best option at this point is:
|
|||
|
||||
+ Fixing WAPBL (e.g. to flush newly allocated/newly written blocks to
|
||||
disk early) has been examined by several people who know the code base
|
||||
and judged difficult. Still, it might be the best way forward.
|
||||
and judged difficult. Also, some other problems have come to light
|
||||
more recently; e.g. PR 50725, PR 47146, and a problem where truncating
|
||||
large sparse files takes ~forever. Also see PR 45676. Still, it might
|
||||
be the best way forward.
|
||||
|
||||
+ There is another journaling FFS; the Harvard one done by Margo
|
||||
Seltzer's group some years back. We have a copy of this, but as it was
|
||||
|
|
Loading…
Reference in New Issue