Berkeley DB must never experience an application crash, especially if a transaction is in progress. If an application using fakefs should crash, all processes using the same fakefs data store will have to be aborted and the fakedmd process restarted.
On the other hand, Berkeley DB provides a robust transaction-oriented database back-end, which provides the benefits of a physical journaling file system.