@GernotS I can somewhat reproduce your panic, although mine dies in ASSERT: ``` assertion failed: spa_feature_is_active(spa, SPA_FEATURE_ENCRYPTION), file: ../../common/fs/zfs/dsl_crypt.c, line: 2530 ```
I have noticed that a pool created like: ``` # zpool create -fd -o feature@encryption=enabled BOOM c2t1d0 # zfs create -o encryption=aes-256-ccm -o keyformat=passphrase BOOM/ccm # zpool export BOOM # zpool import BOOM ; zfs destroy BOOM/ccm ``` will be fine, but if you create it; ``` # zpool create -fd -o feature@encryption=enabled -o feature@async_destroy=enabled BOOM c2t1d0 ``` It will panic. I am not familiar with this area of ZFS, but it would seem that the `dsl_dataset.c` code disables all the features on the pool, then tests if `async_destroy` is set. So the first (delayed) IO will trip over the ASSERT testing feature is set. Ignoring `async_destroy` if dataset is encryption is enabled might just work, but how is this not a problem for other features? But I'm probably guessing wrong. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/124#issuecomment-310239518 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T1625245905c55186-M78e3b85b864ab94df8c5389d Powered by Topicbox: https://topicbox.com
