Some datasets not mounting on startup

[nomenator]

Scale Bluefin.

I have a dataset that has 16 child datasets some of which are used in applications and others in storage. A couple days ago, some of these 16 datasets (but not all) stopped automatically mounting on startup (I experienced this after system update, and now I've restarted the system maybe a dozen times while testing out various solutions). I was unable to establish some rhyme or reason for this - no consistency between these datasets depending on their ACL, whether or not they are used in applications or being shared, nothing clued me in. I removed all shares (smb/nfs), stripped all ACLs. Nothing causes them to automount anymore. Requesting ls through command line on any of them after restart shows empty directory and navigating to the dataset details in GUI displays error libzfs.ZFSException: cannot get used/quota for storage/Nat: dataset is busy and does not display proper details data. However, after manually mounting the dataset I see all the data intact, the application that uses the dataset can access it, and the details show properly. Is there something under the hood that can tell me whether the system tries to mount these datasets and fails, or mounting on these specific datasets has been disabled for some reason? How can I troubleshoot this issue?

 

[winnielinnie]

Are you using encryption in any degree?

 

[nomenator]

Are you using encryption in any degree?

Only zfs encryption by key, no passphrase. The datasets are unlocked at startup, and I did check - some of them are automounted and some are not regardless of the encryption status.

 

[nomenator]

Are you using encryption in any degree?

Curiously, encryption was the problem after all. Earlier, I set up backing up on my application storage dataset, and I created a duplication task for the backup onto the storage dataset. This created an unencrypted child inside the encrypted storage dataset. As soon as I deleted that duplication target, the problem went away.