Muddoggg

1. Safety flow - Confirm ZFS mappings is hidden until Enable ZFS dataset delete is checked -> working - Confirm ZFS rows still require Enable permanent delete before they become actionable -> working 2. Mapping workflow -> all working 3. Discovery vs mapping behavior working 4. ZFS preview and delete working 5. Actual delete behavior DELETE works for both. NOTE: It might still be good to add child datasets to the delete modal for brevity. 6. Case sensitivity Looking great! Thanks.

Before enable: After enable: ZFS mapping shows not selected, and labels make more sense. Both roots selected and save mapping was done without add mapping: Save mappings disabled if one is blank: NOTE: if i click "REMOVE" for the mapping, and click Done and open the modal back up, it is still there: Rescan after mapping save... NOTE: Elements are not selectable on the check box, to quarantine. It seems I can only get the elements selectable when i enable perm delete.... Note: If you click rescan after disabling enable zfs dataset delete, it still shows files: Dry run without recursion: Children added to test_2: Dry run with recursion... NOTE: should it list children datasets? it doesn't currently, but does show recursive text. DELETE of test_1 (no children): NOTE: the final DELETE for test_2 (with child elements) should show something like dry run does that it is recursive, also it's not showing all children that would be deleted... Casing test: Seems like it's working great now! Just a few notes to clean up... Thanks again!

ZFS created: After rescan: Added capital TEST ZFS dataset: Rescan: Added child element to dataset with capital TEST: ZFS found with grep (2 parent, 1 child of TEST): Rescan does NOT pickup child element (this seems correct to me, I don't believe it should)... Dry run result with "test" (no child) ZFS dataset Something I noticed, you cannot delete ZFS dataset even if Enable ZFS dataset delete is enabled, you have to ALSO enable Enable permanent delete... Is that expected? Dry run for perm delete: Delete... I believe the text vebiage is incorrect, it's showing "folders" instead of "datasets" on the top label text and on the delete button. DELETE ran with Error: Dry run for parent with a child dataset only lists the parent dataset: Same for the actual delete: That one errored as well: Not sure what the share root is... and it seems if I change the path at the bottom then click "Use Current Path" and assign it to a path that doesn't contain any datasets, the rescan still shows my datasets. Is that expected? I'm not really sure what this ZFS mappings is, TBH. Might need some explanation... Final Notes: In addition to a dataset having children elements to force '-r', if a dataset has a snapshot, it would require '-r' as well. I didn't test this, because I can't even delete a normal dataset without any children datasets or snapshots yet. Overall, it's looking good! Thanks for the quick reply.

Sure! So my setup is I have all my appdata on a zfs filesystem for my docker and for my vms. mount point: /mnt/docker_vm_nvme/appdata/<app> user share: /mnt/user/appdata/<app> To destroy the dataset, you would do zfs destroy -r docker_vm_nvme/appdata/<app> Note the '-r' for recursive, this is required if the dataset has snapshots or children exist. If not, you do not need '-r'. Important to note zfs is case sensitive, so Sonarr and sonarr would be two different datasets. Let me know if that answers all your questions, thank you

@XCrownedClownsX is there any chance you could add support for ZFS dataset deletes? Thanks so much!

That would work even better!

It would be awesome if the dashboard widget adjustment was no longer stored in cookies in the browser but instead via .cfg on the flash drive so that the dashboard widgets persist layout across all clients.

Hello all- I am seeing a bug on Sonarr that allows you to enable both "Delete empty series" and "Create missing series". I believe this is a bug as only one of them should be allowed to be enabled, similar to binhex-radarr.