friendly, eg if storage restoration is already enabled you mihht not think that you should try to enable it to get this side effect.
In that case, rolling logs will restore the directories just like it works as of now
HA imposes higher restrictions compared to what works as of now. So we might need to do special stuff for HA only. Which might be trying to restore failed directories in the process of transitioning to active (maybe also standby)
From what I read of the code, the standby doesnt seem to bother with setting failed directories since its operations are all read only. So there might be no need for the standby to shutdown gracefully.
If the active moves to SM because of a bad required directory then it should restore all required directories when it goes out of safe mode or else complain and stay in safe mode. All this should happen after the admin has done the necessary pre-requisites and issued a -safeMode leave command.
There's some interaction with fencing, here, though... one likely reason that the NN will lose touch with the shared storage is that another node has requested that the NAS device fence the host. Then, after the failover, the administrator might unfence the host from the NAS, and we don't want the NN to automatically "come back to life" at this point.
Does the NN come back out of safemode automatically or only after an admin command?