August 29, 20241 yr I´m wondering...the idea of having a cache pool (or single disk) is to accelerate the work and then at some point transfering the files to the protected array, I get it. But... My system will store photography/videos in one 4TB name and documents in another 2TB NVME. I'll have an array with 4tb party and two 3TB dives, 6tb storage . I´m planning my setup as such: NVMEs to store/work on. Every night this disks are copied/synced with the array using rsync in the crontab file. The hot/cold storage strategy... Questions: 1. Under these circumstances, does it make any sense to have a cache pool? I´m already working on the fastest disks possible... 2. I´m still in doubt if the array will be XFS or BTRFS, but about the single NVMEs...the 4TB one is currently in APFS format...I can install it as an Unassigned Drive in this format and live it so...will I really gain anything by converting it to XFS or BTRFS? It will be a PITA but doable...speed will be the same I guess because the bottleneck with be the network/thunderbolt connection, but maybe stability would be better in a native format? The other NVME is in EXT4, so Linux native is stable enough? I´m about to build it, so any comments will be greatly appreciated! André Edited August 29, 20241 yr by Botafoguense1965
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.