October 24, 20232 yr I moved around some shares and /anime is now empty. I checked for hidden folders, nothing is inside it. I checked the plugins file activity and open files and nothing is pointing to that share. No docker running is pointing to that share, however I think it's an issue with ZFS. It looks like ZFS is still using the share and therefore, I cannot delete it. How do I fix this? I have other shares I need to remove as well, I assume i will have the same problem. Oct 24 14:13:07 FoxDie shfs: /usr/sbin/zfs unmount 'cache_system/anime' Oct 24 14:13:07 FoxDie shfs: /usr/sbin/zfs destroy 'cache_system/anime' Oct 24 14:13:07 FoxDie root: cannot destroy 'cache_system/anime': dataset is busy Oct 24 14:13:07 FoxDie shfs: retval: 1 attempting 'destroy' Oct 24 14:13:07 FoxDie shfs: /usr/sbin/zfs mount 'cache_system/anime'
October 25, 20232 yr Author 7 hours ago, JorgeB said: Post the output of: zfs list -t all Here is the output:
October 25, 20232 yr Community Expert Try rebooting and after array start type: zfs destroy cache_system/anime to see if it can do it.
October 25, 20232 yr Author 9 minutes ago, JorgeB said: Try rebooting and after array start type: zfs destroy cache_system/anime to see if it can do it. I gave this a try but it's still saying it's busy
October 25, 20232 yr Community Expert There are no snapshots or nested datasets, so something could still be using it, are you certain no container has mappings there? Did you try with the docker service stopped?
October 25, 20232 yr Author Solution 52 minutes ago, JorgeB said: Also try booting in safe mode in case it's a plugin. When you mentioned this I immediately thought of the ZFS Master plugin, which was the culprit. I went into that plugin settings and "Destructive Mode" was set to "No". I changed this to "Yes" and then went back into the share in unraid, and was able to delete it. It seems the plugin prevents deletion even if the share is empty.
October 25, 20232 yr 4 hours ago, Indi said: When you mentioned this I immediately thought of the ZFS Master plugin, which was the culprit. I went into that plugin settings and "Destructive Mode" was set to "No". I changed this to "Yes" and then went back into the share in unraid, and was able to delete it. It seems the plugin prevents deletion even if the share is empty. Hi, ZFS Master plugin developer here. Destructive mode is not what you think; that setting that you just changed only affects the UI; when you change it to "Yes" the ZFS Master plugin shows destructive action elements in the UI (Destroy dataset and other stuff); but the plugin doesn't implement or even have the powers to prevent a dataset from being deleted/modified; quite the opposite, the plugin provides a UI for doing precisely that. Your issue is more related to this: Edited October 25, 20232 yr by Iker
October 25, 20232 yr Author 2 hours ago, Iker said: Hi, ZFS Master plugin developer here. Destructive mode is not what you think; that setting that you just changed only affects the UI; when you change it to "Yes" the ZFS Master plugin shows destructive action elements in the UI (Destroy dataset and other stuff); but the plugin doesn't implement or even have the powers to prevent a dataset from being deleted/modified; quite the opposite, the plugin provides a UI for doing precisely that. Your issue is more related to this: I am a little confused though. I am cleaning up a few other shares and when "Destructive" mode is set to "No" in the plugin I can't delete a share that is in the ZFS cache. When I set this to "Yes" in the plugin, I can delete the share. I am deleting the share via Unraid, by clicking the share and checking Delete, not through the plugin. I just replicated this again so something has to be wrong if the plugin doesn't prevent a dataset from being deleted. I assume that the plugin is somehow holding onto that share so that Unraid sees it as being in use. But changing that setting fixes it, for whatever reason.
June 2, 20242 yr Hi, I just ran into the same issue. Had a few shares that I could not delete whatever I tried. Uninstalling ZFS Master fixed it. Once I knew this I found this thread and reinstalled ZFS Master. Enabling destructive mode does indeed fix it. Why ZFS Master is leaving my dataset "busy" I don't know. Could be I have some browser tab on some machine somewhere that has the ZFS Master gui open and that this is locking the dataset preventing share deletion?
June 24, 20242 yr Hi, From command line or within the plugin, independently from destructive mode, to be able to destroy I need to rename the dataset to something different than a share name. I think the behaviour is because of sshfs, mdm, or something else regarding share mounts. I think that's not a problem, but a concept or a feature 😁 Hope this helps
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.