I have 2 pools, Backup (4Tb, 2 x SSD) and Library (22 Tb, 4 NVMe's).

 

I initially set up the system shares (system, domains, isos and appdata) to be placed on Library because it's the largest pool. However, along the way, the system shares have automatically been moved to Backup, though under the Shares menu they are still showing as being under Library (see screenshot) and upon running `df -h` (see screenshot) they show up as being under Backup.

 

What's the reason behind the automatic migration and, more importantly, how to permanently move them back to Library?

unraid-diagnostics-20241030-1028.zip

They are all set to cache=only on Library, so it wasn't Unraid that moved them, possibly you started the array with the Library pool?

 

To move them, disable Docker and VM services, set all those shares to primary=Library, Secondary=Backup, mover action Backup -> Library, then enable mover logging and run the mover.

 

Note that if there are any duplicate files they won't be moved, also Ubuntu and vmlinux are nested datasets, so they also won't be moved, but they appear to be empty, post new diags after running the mover.

It works beautifully. Thanks for the help.

After I ran `move start`, it migrated everything and left two empty folders in `/mnt/backup/domains`. I tried to remove them manually, but it ended in:

root@unraid:/mnt/backup# rmdir domains/*
rmdir: failed to remove 'domains/Ubuntu': Device or resource busy
rmdir: failed to remove 'domains/vmlinux': Device or resource busy

That's not an issue as they are empty, but will they be removed after a reboot?

I'm not sure whether I started the Library alone, without Backup. That's possibly the case.

1 hour ago, kevin.denver said:

That's not an issue as they are empty, but will they be removed after a reboot?

If /mnt/backup/domains is empty, and because there are nested zfs datasets, you need to use:

 

zfs destroy -r backup/domains

 

 

Great, that did it.

 

A last question on this topic, if I may: when you said "They are all set to cache=only on Library", does that mean there are other choices? I was under the impression that there was 2 modes only, cache and array(?). In my case I do not use arrays but instead I have placed all disks in two separate pools in RAID. Is this a good/stable/advisable config as per the configuration itself (not mentioning redundancy, etc.)?

With v7 you can also use pools as a secondary storage, but using just one pool only is fine, it just depends on your use case, and if all the data has been moved you can set the secondary storage=none for all system shares.