* "Prefer" indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient free space on the Cache disk/pool, create operations will fail with out of space status. * "Only" indicates that all new files and subdirectories must be written to the Cache disk/pool. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. * "Yes" indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. * "No" prohibits new files and subdirectories from being written onto the Cache disk/pool.
You can specify for each "share" if it should be No/Yes/Only/Prefer, explanation of each below (Pulled from my UnRaid install): The mover will not move files that still have an open handle on them (ie. The "sync" (called "mover" in unraid terms) is a process that runs on a schedule you set (most people set it to run at night) that will move data to/from your cache drives to/from your raid array. You can setup a pool of SSD drives and tell different "shares" (think a folder than can span 1 more drives based on rules you set) to use that pool (BTRFS raid-1-type pool, so 2x1TB SSDs = 1TB cache pool). The "sync" command you are talking about is related to the cache drives.
0 kommentar(er)
