This issue was originally found when setting up the LXC plugin, whereby its "lxc" storage directory was exhibiting this issue when stored inside the only pool on the system.
Description
From terminal (or a script or a plugin), creating a directory under a pool will cause that directory to show up as a share, but listed as stored on Array instead of the Pool.
This happens even if you do not have an Array.
In the case where you have no array, the directory is created in the pool, but the system thinks that this directory/share has 0 bytes free.
*You may or may not be able to copy anything to it from terminal for example - I've had it work and I've had it report that the target was full.
In the case where you have an array and a pool, the directory will be created in both the pool and in the Array's FUSE FS (not on the actual disks that make up the array). The system will show the directory/share as having the free space of the Array. You can copy as much data as this reported free space.
Steps to Reproduce
On a system with a single NVME drive formatted as ZFS - No Array
From terminal, create a directory on the pool volume
It gets created (shown as TestfolderZ in this image)
Open the Shares tab in the WebUI to see the directory/share listed as belonging to "Array" (which doesn't exist)
If you check the /mnt/user/ fuse path, you can see the directory appears there as well, but not as a link like all the other shares
The directory/share's settings correctly show that it really belongs under the pool
Making an edit to the settings, such as adding a Comment, and then applying, corrects the issue:
Continued in next post...
Recommended Comments
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.