summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordholland <dholland@NetBSD.org>2016-05-05 06:17:45 +0000
committerdholland <dholland@NetBSD.org>2016-05-05 06:17:45 +0000
commitea4e0fbee54da4c78c1803a0b675273aa4875375 (patch)
tree4875550438737c0484aca723cf3892d8eb605df8
parente0acaa3c2345db96a6b0dd3e3619824a32070b18 (diff)
mention some of the other known severe wapbl problems
-rw-r--r--doc/roadmaps/storage7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/roadmaps/storage b/doc/roadmaps/storage
index b48053c933a..5e6feb10b3b 100644
--- a/doc/roadmaps/storage
+++ b/doc/roadmaps/storage
@@ -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