ZFS Mover between two pools.

[tryhardcodemaster]

Hi all,

 

I don't know if this is a known or expected behavior in unRAID 7b2, or if it is because I upgraded from 6.11, but here's the issue.

 

I have a share called media. The primary storage is the "cache" pool, a ZFS mirror, and the secondary storage is the "data" pool, 2 ZFS mirror VDEVs. It is set to move from cache to data.

 

The share does not exist on the cache pool. On the data pool, there is a media zfs dataset. If I select to move from one to the other, it will create the dataset on the target, move the files, and then destroy the dataset on the other.

 

Aug 15 22:46:24 BLOCK0 shfs: /usr/sbin/zfs unmount 'cache/media' 2>&1
Aug 15 22:46:24 BLOCK0 shfs: /usr/sbin/zfs destroy 'cache/media' 2>&1
Aug 15 22:46:24 BLOCK0 move: mover: finished

 

Is this expected in the current 7.0 beta 2? I'm used to the older unRAID, where the share exists on both cache and data and mover will just move the files from one to the other, while new data gets written to cache.

 

If I write to /mnt/user/media, it will only write to the "data" pool since the dataset doesn't exist on cache.

 

I apologize if this has already been discussed. I searched on the forums but couldn't find anything with "mover" and "destroy"

[JorgeB]

8 hours ago, tryhardcodemaster said:

Is this expected in the current 7.0 beta 2?

Yes, and it was the same with v6.12, if a share was for example moved to the array and no longer had any files on the pool, the dataset was destroyed.

[tryhardcodemaster]

On 8/16/2024 at 7:58 AM, JorgeB said:

Yes, and it was the same with v6.12, if a share was for example moved to the array and no longer had any files on the pool, the dataset was destroyed.

But say if you have your primary storage marked as the cache, should it be destroyed if there are no files on it? If new files are written, it seems to be writing directly to the secondary storage, rather than writing to the cache.

[JorgeB]

13 hours ago, tryhardcodemaster said:

But say if you have your primary storage marked as the cache, should it be destroyed if there are no files on it?

Yes.

 

13 hours ago, tryhardcodemaster said:

If new files are written

It will create a dataset again.

[tryhardcodemaster]

On 8/19/2024 at 11:42 AM, JorgeB said:

Yes.

 

It will create a dataset again.

I just did some testing.

 

On my pool named "cache", it does not recreate the dataset, but on my pool named "nvmepool", it does create the dataset when set to primary. I'm utterly confused. Time for some more testing.

[JorgeB]

9 hours ago, tryhardcodemaster said:

On my pool named "cache", it does not recreate the dataset

How are you writing to the share?

[tryhardcodemaster]

On 8/21/2024 at 9:00 AM, JorgeB said:

How are you writing to the share?

Writing to /mnt/user/media.

 

I figured out the issue. The minimum free space being automatically calculated was 1.5TB, but the cache pool is only 500GB. If it set the minimum free space down to 100GB, it would start writing to the cache pool for new files, rather than directly to the data pool.