- Solved
- Minor
Had a share named temp.
Main storage was zfs pool, named "cache".
Secondary storage, was the main unraid array.
Set the secondary storage to "none", and clicked saved.
Instead, of expected confirmation, received popup message saying share was deleted.
Found broken symlink under /mnt/user for temp, pointing to non-existent directory /mnt/cache/temp.
What I believe happened here-
There were no files on the "cache" pool. The ZFS dataset didn't even exist yet, as I had not written anything to it.
There were, however files on the unraid array.
So, when I remove the secondary storage, there was "nothing", hence the confusing message. However, the files still do exist on /mnt/disk1/temp, as I would expect.
TLDR / To Reproduce-
Create a share on the array. Add a few files.
Update the share, to have primary storage pointing at a zfs pool, and secondary storage, on the array, with mover action set move files to array.
Save. Do note, zfs list will not yet show the dataset, until something has been written to it.
But, dont' write anything to it.
Instead, update the share again. Remove the secondary storage (array). Save.
You will be presented with a broken symlink, and a "Deleted" dialog.
-
1
