1) Start 2 NN's in active standby mode
2) Remove write permissions from shared edits dir
3) Upon log roll triggered by standby, the active gets error when finalizing the edit logs
4) The error exception is caught way up on the stack and error does not get reported against the bad shared edits dir
This happens because error reporting happens when FSImage.rollEditLogs() calls storage.writeTransactionIdFileToStorage() which is called after FSEDit.rollEditLogs(). The error in FSEdit.rollEditLogs() raises an exception that is not handled in FSImage.rollEditLogs() and hence storage.writeTransactionIdFileToStorage() does not get called and no error is reported. The bad directory continues to remain in FSImage.storage.