[6.12.10] Incorrect dataset creation on ZFS - different location

What were the share settings for that share when it was created? You can post a screenshot of the current settings if they were not changed. 

They have not been changed, I'm waiting to see what Lime has to say about it

 

I cannot reproduce that, are you sure the share settings used were those? Or that the dataset didn't already exist?

 

Creating a new share with primary storage set to a pool only creates the dataset in the pool:

 

 

Try deleting the share and recreating again double checking the settings

 

 

After remove "syncthing" share and dataset:

 

 

Settings when creating a share again:

 

And now it is indeed ok.

 

I don't know what could have caused the previous degeneration.

I did it the same way, only in addition I set the minimum free size, but I already checked and it does not change anything.

Ok, I'm going to keep an eye on this because it worries me.

 

Edited April 18 by jaclas

OK, going to close this for now, please re-open and let us know if you find anything else.

So I think I know what might have caused that, which is that in the beginning the share was configured with the Secondary Storage with Mover. I just experienced the same behavior with `domains` share.

 

Even though it is stored ONLY in Cache now (I changed that) the calculation shows it resides in the Array:

 

This is also illustrated in the mount table:

 

I want it to be totally located in Cache, because otherwise using VMs keeps spinning my Array. What can I do other than removing a share and creating another one? I have multiple VMs already configured there.

 

38 minutes ago, totuk said:

What can I do

Attach Diagnostics to your NEXT post in this thread. 

2 hours ago, totuk said:

So I think I know what might have caused that, which is that in the beginning the share was configured with the Secondary Storage with Mover. I just experienced the same behavior with `domains` share.

 

Even though it is stored ONLY in Cache now (I changed that) the calculation shows it resides in the Array:

You should not change it to only be in the cache until you have successfully moved all the files to the cache.  Changing to that setting only applies to where NEW files are stored and does not cause existing files to automatically be moved.   Mover ignores any shares which are set to use only the cache even when there are files for that share that are located elsewhere.

4 hours ago, totuk said:

which is that in the beginning the share was configured with the Secondary Storage with Mover.

This is normal, if a share is created with primary storage=pool and secondary storage=array, it will first be created on the array, after any new write to it, the share (dataset) will also be created on the pool.

@itimpi 

@JorgeB

Thank you guys. That helped. I moved my `domains` to `domains_old`, then created a new Share located ONLY in Cache this time from the beginnig and mv-ed all the data from `domains_old` to new `domains`. All the rest came with no issues.