Cannot write/create/delete on parent dataset

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
If you think there is a bug, perhaps file a bug report on our jira instance rather than upstream issue report with openzfs. Opensource projects usually have limited resources for delving into user issues, and we're better equipped to quickly identify / fix problems in our product.

That said, you can PM me a debug please and I'll take a look at it as I have time. That said, the general advice upstream is sound. It's better idea to not write data to /mnt/secure2 or expose it through NFS / SMB.
 

radomirpolach

Explorer
Joined
Feb 13, 2022
Messages
71
If you think there is a bug, perhaps file a bug report on our jira instance rather than upstream issue report with openzfs. Opensource projects usually have limited resources for delving into user issues, and we're better equipped to quickly identify / fix problems in our product.

That said, you can PM me a debug please and I'll take a look at it as I have time. That said, the general advice upstream is sound. It's better idea to not write data to /mnt/secure2 or expose it through NFS / SMB.
How can I create debug for you?

Btw, I cannot write data to the dataset, so no issue there. The child datasets on the other hand works without issues.

Btw, the issue is most likely caused by my earlier attempt to move ix-applications dataset to this pool. Both pools were encrypted, and it didn't work (hanged), but something apparently happened to my root dataset: https://ixsystems.atlassian.net/browse/NAS-118328
 

radomirpolach

Explorer
Joined
Feb 13, 2022
Messages
71
Click System->Advanced->Save Debug
I have a better thing now. I have dumped my root dataset and because it doesn't contain almost data, just directories and one file, it is only 54 kB, I imported him elsewhere and the issue persists. I can share this dataset, and it's encryption key and 3rd party can test it.
 
Top