All my shares just used primary storage and had exclusive access = yes, however the recent upgrade to 7.0.0 allowed me to free up some old sata ssd's which I was using as the Array device and were doing nothing.

 

I want to test a shares performance by adding these newly available drives as the primary storage aka cache for a pre-existing share.  I can amend the share configuration with no issue selecting the new pool as primary and the old/original pool as secondary.  This saves, the /mnt/user directory no longer symlinks to the pool device so exclusive access for the share now = no, so far so good.

 

I suspect my test case is wrong, should I be writing new files/folders to the share name under /mnt/user and should I expect them to appear in /mnt/new-primary-cache-pool until the mover process runs which then moves them to the old/original pool device under /mnt?

Edited January 20, 20251 yr by KillerK
typo

Sorry, but I don't understand the question, please clarify, new writes to that share (using /mnt/user/share_name) will go to primary storage.

 

 

So I have a zpool called 'blacknet' which is the original primary storage for a share called 'multimedia'.

 

I've just created a new zpool called 'blacknet_cache' and have amended the 'multimedia' share as per the below...

So I then do the following...

# cd /mnt/user/multimedia/
# mkdir share_test
# cd share_test/
# touch tester.test
# ls -l
total 1
-rw-rw-rw- 1 root root 0 Jan 20 13:26 tester.test
# ls -l /mnt/blacknet_cache/
total 0
# ls -l /mnt/blacknet/multimedia/
total 1
drwxrwxrwx   2 root   root    3 Jan 20 13:26 share_test/
# ls -l /mnt/blacknet/multimedia/share_test/
total 1
-rw-rw-rw- 1 root root 0 Jan 20 13:26 tester.test

 

This shows that new folders and files are still being directly written to the blacknet zpool which is configured as the secondary storage for the share.  The mover process is currently set to run every 2 hours and hasn't run here yet so thats not the problem.  The only other nuance I have which could be involved here is that previously I created a zfs dataset called multimedia on the blacknet pool with a mountpoint of /mnt/blacknet/multimedia.  Could this be causeing this behaviour?

 

EDIT:

Creating a new share and works as expected with data first written to blacknet_cache and the mover then moves it to blacknet when triggered.  So my problem only relates to a pre-existing share.

Edited January 20, 20251 yr by KillerK
typo & update