1$NetBSD: storage,v 1.15 2016/05/17 21:03:36 christos Exp $ 2 3NetBSD Storage Roadmap 4====================== 5 6This is a small roadmap document, and deals with the storage and file 7systems side of the operating system. It discusses elements, projects, 8and goals that are under development or under discussion; and it is 9divided into three categories based on perceived priority. 10 11The following elements, projects, and goals are considered strategic 12priorities for the project: 13 14 1. Improving iscsi 15 2. nfsv4 support 16 3. A better journaling file system solution 17 4. Getting zfs working for real 18 5. Seamless full-disk encryption 19 6. Finish tls-maxphys 20 21The following elements, projects, and goals are not strategic 22priorities but are still important undertakings worth doing: 23 24 7. nvme support 25 8. lfs64 26 9. Per-process namespaces 27 10. lvm tidyup 28 11. Flash translation layer 29 12. Shingled disk support 30 13. ext3/ext4 support 31 14. Port hammer from Dragonfly 32 15. afs maintenance 33 16. execute-in-place 34 17. extended attributes for acl and capability storage 35 36The following elements, projects, and goals are perhaps less pressing; 37this doesn't mean one shouldn't work on them but the expected payoff 38is perhaps less than for other things: 39 40 18. coda maintenance 41 42 43Explanations 44============ 45 461. Improving iscsi 47------------------ 48 49Both the existing iscsi target and initiator are fairly bad code, and 50neither works terribly well. Fixing this is fairly important as iscsi 51is where it's at for remote block devices. Note that there appears to 52be no compelling reason to move the target to the kernel or otherwise 53make major architectural changes. 54 55 - As of November 2015 nobody is known to be working on this. 56 - There is currently no clear timeframe or release target. 57 - Contact agc for further information. 58 59 602. nfsv4 support 61---------------- 62 63nfsv4 is at this point the de facto standard for FS-level (as opposed 64to block-level) network volumes in production settings. The legacy nfs 65code currently in NetBSD only supports nfsv2 and nfsv3. 66 67The intended plan is to port FreeBSD's nfsv4 code, which also includes 68nfsv2 and nfsv3 support, and eventually transition to it completely, 69dropping our current nfs code. (Which is kind of a mess.) So far the 70only step that has been taken is to import the code from FreeBSD. The 71next step is to update that import (since it was done a while ago now) 72and then work on getting it to configure and compile. 73 74 - As of November 2015 nobody is working on this, and a volunteer to 75 take charge is urgently needed. 76 - There is no clear timeframe or release target, although having an 77 experimental version ready for -8 would be great. 78 - Contact dholland for further information. 79 80 813. A better journaling file system solution 82------------------------------------------- 83 84WAPBL, the journaling FFS that NetBSD rolled out some time back, has a 85critical problem: it does not address the historic ffs behavior of 86allowing stale on-disk data to leak into user files in crashes. And 87because it runs faster, this happens more often and with more data. 88This situation is both a correctness and a security liability. Fixing 89it has turned out to be difficult. It is not really clear what the 90best option at this point is: 91 92+ Fixing WAPBL (e.g. to flush newly allocated/newly written blocks to 93disk early) has been examined by several people who know the code base 94and judged difficult. Also, some other problems have come to light 95more recently; e.g. PR 50725, PR 47146, and a problem where truncating 96large sparse files takes ~forever. Also see PR 45676. Still, it might 97be the best way forward. 98 99+ There is another journaling FFS; the Harvard one done by Margo 100Seltzer's group some years back. We have a copy of this, but as it was 101written in BSD/OS circa 1999 it needs a lot of merging, and then will 102undoubtedly also need a certain amount of polishing to be ready for 103production use. It does record-based rather than block-based 104journaling and does not share the stale data problem. 105 106+ We could bring back softupdates (in the softupdates-with-journaling 107form found today in FreeBSD) -- this code is even more complicated 108than the softupdates code we removed back in 2009, and it's not clear 109that it's any more robust either. However, it would solve the stale 110data problem if someone wanted to port it over. It isn't clear that 111this would be any less work than getting the Harvard journaling FFS 112running... or than writing a whole new file system either. 113 114+ We could write a whole new journaling file system. (That is, not 115FFS. Doing a new journaling FFS implementation is probably not 116sensible relative to merging the Harvard journaling FFS.) This is a 117big project. 118 119Right now it is not clear which of these avenues is the best way 120forward. Given the general manpower shortage, it may be that the best 121way is whatever looks best to someone who wants to work on the 122problem. 123 124 - As of November 2015 nobody is working on fixing WAPBL. There has 125 been some interest in the Harvard journaling FFS but no significant 126 progress. Nobody is known to be working on or particularly 127 interested in porting softupdates-with-journaling. And, while 128 dholland has been mumbling for some time about a plan for a 129 specific new file system to solve this problem, there isn't any 130 realistic prospect of significant progress on that in the 131 foreseeable future, and nobody else is known to have or be working 132 on even that much. 133 - There is no clear timeframe or release target; but given that WAPBL 134 has been disabled by default for new installs in -7 this problem 135 can reasonably be said to have become critical. 136 - Contact joerg or martin regarding WAPBL; contact dholland regarding 137 the Harvard journaling FFS. 138 139 1404. Getting zfs working for real 141------------------------------- 142 143ZFS has been almost working for years now. It is high time we got it 144really working. One of the things this entails is updating the ZFS 145code, as what we have is rather old. The Illumos version is probably 146what we want for this. 147 148 - There has been intermittent work on zfs, but as of November 2015 149 nobody is known to be actively working on it 150 - There is no clear timeframe or release target. 151 - Contact riastradh or ?? for further information. 152 153 1545. Seamless full-disk encryption 155-------------------------------- 156 157(This is only sort of a storage issue.) We have cgd, and it is 158believed to still be cryptographically suitable, at least for the time 159being. However, we don't have any of the following things: 160 161+ An easy way to install a machine with full-disk encryption. It 162should really just be a checkbox item in sysinst, or not much more 163than that. 164 165+ Ideally, also an easy way to turn on full-disk encryption for a 166machine that's already been installed, though this is harder. 167 168+ A good story for booting off a disk that is otherwise encrypted; 169obviously one cannot encrypt the bootblocks, but it isn't clear where 170in boot the encrypted volume should take over, or how to make a best 171effort at protecting the unencrypted elements needed to boot. (At 172least, in the absence of something like UEFI secure boot combined with 173an cryptographic oracle to sign your bootloader image so UEFI will 174accept it.) There's also the question of how one runs cgdconfig(8) and 175where the cgdconfig binary comes from. 176 177+ A reasonable way to handle volume passphrases. MacOS apparently uses 178login passwords for this (or as passphrases for secondary keys, or 179something) and this seems to work well enough apart from the somewhat 180surreal experience of sometimes having to log in twice. However, it 181will complicate the bootup story. 182 183Given the increasing regulatory-level importance of full-disk 184encryption, this is at least a de facto requirement for using NetBSD 185on laptops in many circumstances. 186 187 - As of November 2015 nobody is known to be working on this. 188 - There is no clear timeframe or release target. 189 - Contact dholland for further information. 190 191 1926. Finish tls-maxphys 193--------------------- 194 195The tls-maxphys branch changes MAXPHYS (the maximum size of a single 196I/O request) from a global fixed constant to a value that's probed 197separately for each particular I/O channel based on its 198capabilities. Large values are highly desirable for e.g. feeding large 199disk arrays but do not work with all hardware. 200 201The code is nearly done and just needs more testing and support in 202more drivers. 203 204 - As of November 2015 nobody is known to be working on this. 205 - There is no clear timeframe or release target. 206 - Contact tls for further information. 207 208 2097. nvme suppport 210---------------- 211 212nvme ("NVM Express") is a hardware interface standard for PCI-attached 213SSDs. NetBSD now has a driver for these; however, it was ported from 214OpenBSD and is not (yet) MPSAFE. This is, unfortunately, a fairly 215serious limitation given the point and nature of nvme devices. 216 217Relatedly, the I/O path needs to be restructured to avoid software 218bottlenecks on the way to an nvme device: they are fast enough that 219things like disksort() do not make sense. 220 221Semi-relatedly, it is also time for scsipi to become MPSAFE. 222 223 - As of May 2016 a port of OpenBSD's driver has been commited. This 224 will be in -8. 225 - The nvme driver is a backend to ld(4) which is MPSAFE, but we still 226 need to attend to I/O path bottlenecks. Better instrumentation 227 is needed. 228 - There is no clear timeframe or release target for these points. 229 - Contact msaitoh or agc for further information. 230 231 2328. lfs64 233-------- 234 235LFS currently only supports volumes up to 2 TB. As LFS is of interest 236for use on shingled disks (which are larger than 2 TB) and also for 237use on disk arrays (ditto) this is something of a problem. A 64-bit 238version of LFS for large volumes is in the works. 239 240 - As of November 2015 dholland is working on this. 241 - It is close to being ready for at least experimental use and is 242 expected to be in 8.0. 243 - Responsible: dholland 244 245 2469. Per-process namespaces 247------------------------- 248 249Support for per-process variation of the file system namespace enables 250a number of things; more flexible chroots, for example, and also 251potentially more efficient pkgsrc builds. dholland thought up a 252somewhat hackish but low-footprint way to implement this. 253 254 - As of November 2015 dholland is working on this. 255 - It is scheduled to be in 8.0. 256 - Responsible: dholland 257 258 25910. lvm tidyup 260-------------- 261 262[agc says someone should look at our lvm stuff; XXX fill this in] 263 264 - As of November 2015 nobody is known to be working on this. 265 - There is no clear timeframe or release target. 266 - Contact agc for further information. 267 268 26911. Flash translation layer 270--------------------------- 271 272SSDs ship with firmware called a "flash translation layer" that 273arbitrates between the block device software expects to see and the 274raw flash chips. FTLs handle wear leveling, lifetime management, and 275also internal caching, striping, and other performance concerns. While 276NetBSD has a file system for raw flash (chfs), it seems that given 277things NetBSD is often used for it ought to come with a flash 278translation layer as well. 279 280Note that this is an area where writing your own is probably a bad 281plan; it is a complicated area with a lot of prior art that's also 282reportedly full of patent mines. There are a couple of open FTL 283implementations that we might be able to import. 284 285 - As of November 2015 nobody is known to be working on this. 286 - There is no clear timeframe or release target. 287 - Contact dholland for further information. 288 289 29012. Shingled disk support 291------------------------- 292 293Shingled disks (or more technically, disks with "shingled magnetic 294recording" or SMR) can only write whole tracks at once. Thus, to 295operate effectively they require translation support similar to the 296flash translation layers found in SSDs. The nature and structure of 297shingle translation layers is still being researched; however, at some 298point we will want to support these things in NetBSD. 299 300 - As of November 2015 one of dholland's coworkers is looking at this. 301 - There is no clear timeframe or release target. 302 - Contact dholland for further information. 303 304 30513. ext3/ext4 support 306--------------------- 307 308We would like to be able to read and write Linux ext3fs and ext4fs 309volumes. (We can already read clean ext3fs volumes as they're the same 310as ext2fs, modulo volume features our ext2fs code does not support; 311but we can't write them.) 312 313Ideally someone would write ext3 and/or ext4 code, whether integrated 314with or separate from the ext2 code we already have. It might also 315make sense to port or wrap the Linux ext3 or ext4 code so it can be 316loaded as a GPL'd kernel module; it isn't clear if that would be more 317or less work than doing an implementation. 318 319Note however that implementing ext3 has already defeated several 320people; this is a harder project than it looks. 321 322 - As of May 2016 there is a GSoC project to implement read-only ext4 323 support, but (it not being summer yet) no particular progress. 324 - There is no clear timeframe or release target. 325 - Contact ?? for further information. 326 327 32814. Port hammer from Dragonfly 329------------------------------ 330 331While the motivation for and role of hammer isn't perhaps super 332persuasive, it would still be good to have it. Porting it from 333Dragonfly is probably not that painful (compared to, say, zfs) but as 334the Dragonfly and NetBSD VFS layers have diverged in different 335directions from the original 4.4BSD, may not be entirely trivial 336either. 337 338 - As of November 2015 nobody is known to be working on this. 339 - There is no clear timeframe or release target. 340 - There probably isn't any particular person to contact; for VFS 341 concerns contact dholland or hannken. 342 343 34415. afs maintenance 345------------------- 346 347AFS needs periodic care and feeding to continue working as NetBSD 348changes, because the kernel-level bits aren't kept in the NetBSD tree 349and don't get updated with other things. This is an ongoing issue that 350always seems to need more manpower than it gets. It might make sense 351to import some of the kernel AFS code, or maybe even just some of the 352glue layer that it uses, in order to keep it more current. 353 354 - jakllsch sometimes works on this. 355 - We would like every release to have working AFS by the time it's 356 released. 357 - Contact jakllsch or gendalia about AFS; for VFS concerns contact 358 dholland or hannken. 359 360 36116. execute-in-place 362-------------------- 363 364It is likely that the future includes non-volatile storage (so-called 365"nvram") that looks like RAM from the perspective of software. Most 366importantly: the storage is memory-mapped rather than looking like a 367disk controller. There are a number of things NetBSD ought to have to 368be ready for this, of which probably the most important is 369"execute-in-place": when an executable is run from such storage, and 370mapped into user memory with mmap, the storage hardware pages should 371be able to appear directly in user memory. Right now they get 372gratuitously copied into RAM, which is slow and wasteful. There are 373also other reasons (e.g. embedded device ROMs) to want execute-in- 374place support. 375 376Note that at the implementation level this is a UVM issue rather than 377strictly a storage issue. 378 379Also note that one does not need access to nvram hardware to work on 380this issue; given the performance profiles touted for nvram 381technologies, a plain RAM disk like md(4) is sufficient both 382structurally and for performance analysis. 383 384 - As of November 2015 nobody is known to be working on this. Some 385 time back, uebayasi wrote some preliminary patches, but they were 386 rejected by the UVM maintainers. 387 - There is no clear timeframe or release target. 388 - Contact dholland for further information. 389 390 39117. use extended attributes for ACL and capability storage 392---------------------------------------------------------- 393 394Currently there is some support for extended attributes in ffs, 395but nothing really uses it. I would be nice if we came up with 396a standard format to store ACL's and capabilities like Linux has. 397The various tools must be modified to understand this and be able 398to copy them if requested. Also tools to manipulate the data will 399need to be written. 400 40118. coda maintenance 402-------------------- 403 404Coda only sort of works. [And I think it's behind relative to 405upstream, or something of the sort; XXX fill this in.] Also the code 406appears to have an ugly incestuous relationship with FFS. This should 407really be cleaned up. That or maybe it's time to remove Coda. 408 409 - As of November 2015 nobody is known to be working on this. 410 - There is no clear timeframe or release target. 411 - There isn't anyone in particular to contact. 412 - Circa 2012 christos made it work read-write and split it 413 into modules. Since then christos has not tested it. 414 415Alistair Crooks, David Holland 416Fri Nov 20 02:17:53 EST 2015 417Sun May 1 16:50:42 EDT 2016 (some updates) 418 419