[src/trunk]: src/doc/roadmaps mention some of the other known severe wapbl pr...

[dholland <dholland%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/ef7a4f585f09
branches:  trunk
changeset: 345058:ef7a4f585f09
user:      dholland <dholland%NetBSD.org@localhost>
date:      Thu May 05 06:17:45 2016 +0000

description:
mention some of the other known severe wapbl problems

diffstat:

 doc/roadmaps/storage |  7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diffs (21 lines):

diff -r 393116c7efd6 -r ef7a4f585f09 doc/roadmaps/storage
--- a/doc/roadmaps/storage      Thu May 05 02:12:21 2016 +0000
+++ b/doc/roadmaps/storage      Thu May 05 06:17:45 2016 +0000
@@ -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 @@
 
 + 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