Adam Simpkins 4a6aaa5de4 load all materialized inodes when starting a mount point ... Summary: As part of the mount process, make sure we load InodeBase objects for all files in the mount that are already materialized. Other parts of the code assume that InodeBase objects are always loaded for materialized files. We never unload materialized inodes, but if the mount point was unmounted then remounted we previously did not ensure to load the materialized InodeBase objects. This diff makes sure we load all materialized inodes before starting the mount. Reviewed By: bolinfest Differential Revision: D4461193 fbshipit-source-id: 70d06fd01e2df333ce2816d5d7a392b0a5d6e1e6		2017-01-25 16:56:12 -08:00
..
cli	allow interpolating USER and HOME in the ClientConfig class	2017-01-23 23:54:38 -08:00
config	allow interpolating USER and HOME in the ClientConfig class	2017-01-23 23:54:38 -08:00
inodes	load all materialized inodes when starting a mount point	2017-01-25 16:56:12 -08:00
integration	change systemConfigDir to etcEdenDir	2017-01-23 23:54:38 -08:00
journal	update all copyright statements to "2016-present"	2017-01-20 22:03:02 -08:00
model	fix a variety of lint issues	2017-01-23 18:03:09 -08:00
rocksdb	update all copyright statements to "2016-present"	2017-01-20 22:03:02 -08:00
service	load all materialized inodes when starting a mount point	2017-01-25 16:56:12 -08:00
store	update all copyright statements to "2016-present"	2017-01-20 22:03:02 -08:00
testharness	implement Future-based recursive Inode lookup	2017-01-25 16:56:12 -08:00