Hi @gea ,
have been updated my home system from omnios-r151034 -> omnios-r151038.
In there are two data pools: tank1 SSD based, tank2 spinning drive based.
On each an encrypted auto mounted file systems, tank1 with a lot if child file systems (inherited encryption). tank2 without childs.
L1:L2 key setup scenario on local folders, both mounted smb shares from remote, geo separated servers. (unchanged setup from above)
Since my upgrade encrypted file system only on tank2 doesn't auto mount anymore.
At the past - before update - rarely both file systems are not auto mounted due to some timing issues: smb not yet mounted at unlock request; I thought. Reboot or manual unlock fixed it.
Manual unlocking of file system on tank2 fix it currently too, but it is consequentially not auto mounted.
Do you have any hints for debugging here time critical behavior?
have been updated my home system from omnios-r151034 -> omnios-r151038.
In there are two data pools: tank1 SSD based, tank2 spinning drive based.
On each an encrypted auto mounted file systems, tank1 with a lot if child file systems (inherited encryption). tank2 without childs.
L1:L2 key setup scenario on local folders, both mounted smb shares from remote, geo separated servers. (unchanged setup from above)
Since my upgrade encrypted file system only on tank2 doesn't auto mount anymore.
At the past - before update - rarely both file systems are not auto mounted due to some timing issues: smb not yet mounted at unlock request; I thought. Reboot or manual unlock fixed it.
Manual unlocking of file system on tank2 fix it currently too, but it is consequentially not auto mounted.
Do you have any hints for debugging here time critical behavior?