Description
Internal testing revealed an issue where, after upgrading from an earlier release, we always fail to save a correct PB-based fsimage (namely, missing inodes leading to an inconsistent namespace). This results in substantial data loss, since the upgraded fsimage is broken, as well as the fsimages generated by saveNamespace and checkpointing.
This ended up being a bug in the old fsimage loading code, patch coming.